12:18pm, MartÃn Ferrari wrote:
Also, I found today the Elizabeth Mattijsen's forks.pm module, and
read that it uses TCP communication (why not UNIX, or -again- mmap?).
Anyway, that seems to me the best approach, as it would be lighter
than ithreads, and I just need to pass messages and a couple of
Try Elizabeth M's forks package. It's designed as a drop-in replacement for
threads, and has better memory usage in a lot of cases.
3:28pm, Jose L. Hernandez wrote:
> Hi,
>
> I'm working on a server application based on the boss-worker threads model.
> My problem is that the worker threads use a
race threaded-script.pl),
or for Solaris (and others) truss. If you're on a Windows box, um, er,
there's probably something to do the same thing.
If you're unfamiliar with these tools, they basically start the program in
question, and then show you all the system calls that are being made. It may
help you to see what's going on behind the scenes.
Paul Archer
Yesterday, Steve Schein wrote:
> Launch the TCP socket and both UDP sockets on threads spawned from the
> main program and keeping them open to perform on-going tasks which
> primarily includes passing data back to the main program for two of the
> sockets and sending messages from the main progra
tible, or for some other reason? I understand
Unix sockets are typically a good bit more efficient that TCP sockets on a
local machine.
Thanks,
Paul Archer
--
Reporter: "What do you think will be the biggest problem
in computing in the 90's?"
Paul Boutin: "There are only 17,000 three-letter acronyms."
--
Why are you detaching your thread? I'd have to reread the docs, but I think
that's your problem. If you detach your thread, then the boss thread can't
keep track of it.
>From perlthrtut:
Ignoring A Thread
join() does three things: it waits for a thread to exit, cleans up
after it, and ret
