At 08:40 -0500 8/31/03, Paul Archer wrote:
...Or
use Thread::Enqueue, and enqueue a value in one thread, then dequeue it in
another.
Actually, that would be Thread::Queue (standard in the Perl
distribution) or Thread::Queue::Any from CPAN (if you're interested
in passing something more than a sim
At 21:08 + 8/30/03, Steve Schein wrote:
The challenge: Using ithreads for TCP and UDP sockets
- client:
Multiple (should scale to thousands) Java apps. running mostly on PC's
- program:
Large Perl program connected to a MySQL database and Apache server. The
program is intended to allow for lo
At 08:36 -0500 8/31/03, Paul Archer wrote:
10:48am, Elizabeth Mattijsen wrote:
> I'm afraid these prerequisites will disqualify using Perl ithreads
for your application in a production setting. This is caused by the
fact that each Perl ithread gets a _copy_ of all data-structures in
> each thr
At 09:17 + 8/31/03, Steve Schein wrote:
> If you're going to need thousands of threads, you're going to need a
lot of RAM. And the copying of data becomes a considerable CPU
burden as well. But I don't need a lot of data, you say. Well, you
do need modules, and modules contain subroutine
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
10:48am, Elizabeth Mattijsen wrote:
> I'm afraid these prerequisites will disqualify using Perl ithreads
> for your application in a production setting. This is caused by the
> fact that each Perl ithread gets a _copy_ of all data-structures in
> each thread.
Thanks for the insight into this asp
Liz:
Thank you for your quick response to my questions.
> I'm afraid these prerequisites will disqualify using Perl ithreads
> for your application in a production setting. This is caused by the
> fact that each Perl ithread gets a _copy_ of all data-structures in
> each thread. In practic
All:
NOTE: Thank you to EM for informing me about this mailing list. I had
no idea that such an atomically sliced forum existed but I'm certainly
glad it does! Imagine, people gathered to discuss only Perl
ithreads... Way cool. Anyhow...
The challenge: Using ithreads for TCP and UDP sockets
