Re: Domain scokets? ceptcl?

On Jul 31, 9:32 pm, "Gerald W. Lester" <Gerald.Les...@xxxxxxx> wrote:
graeme.piete...@xxxxxxxxx wrote:
On Jul 31, 6:38 pm, "Gerald W. Lester" <Gerald.Les...@xxxxxxx> wrote:
graeme.piete...@xxxxxxxxx wrote:
What ways of using unix domain sockets from Tcl are available? ceptcl
seems to have been at 0.3 for a long time.
I found at least one extension that uses them (libmsgque), but it
seems to be doing so from C, not TCL (except indirectly).
I want a fast way of a process to communicate with children (forked
using hte fork command from Expect or TclX if it works for me). Other
methods might work for me.
Well the two common ones are pipes between parent and child, or socket on
How fast are pipes? I might run into performance problems with this
later. yes, I know, premature optimisation, but I would rather know
the potential problem is solveable before I start.
127.0.0.1 (or localhost) on a know port (note -- the parent can use dynamic
port allocation and pass the actual port the children as a command line arg
Neat way to do it, but that is definitely slower than unix domain
sockets

I seriously doubt either of the solutions I propose will be the bottle neck
in what you are doing.

There are already a bit of apssing around of the data causing latency:
normally I would not worry about it.


My suggestion is isloate your interprocess communication by abstracting it
into one or two procedures -- then you can switch as desired. This also has
Will do (easy to do actually).

the advantage of allowing you to take advantage of the platform you are on.

Note -- the socket solution is totally platform independent and can be
easily modified if to deal with agents on other boxes instead of just
children on your box.


--
+--------------------------------+---------------------------------------+
| Gerald W. Lester |
|"The man who fights for his ideals is the man who is alive." - Cervantes|
+------------------------------------------------------------------------+
Thanks, going with pipes. A bit of Googling turned up some numbers,
and they are more than fast enough not to be a bottle neck.

This is one I should have been able to solve for myself - if I had
ever read the man page for open properly! I am all the more grateful
for the help. Thanks.
.

Quantcast