[ale] What to use

[Christopher Fowler]

On Tue, 2003-04-22 at 20:25, John Wells wrote:
> I suspect Perl 6 is going to address a lot of the common complaints of
> Perl.  It's really a great language (the swiss army chainsaw, as they
> say), and can be used very productively for enterprise applications.
> 

I think my concern here is that I may possibly have 1000 TCP connection
coming from one perl script.  I will then use select() in the perl to
multi-plex the data streams. The problem is that there could be 125
remote devices. If one remote device goes down then perl will have 8
connections still open to that device in a read mode.  In theory, those
connection will not terminate until the  KEEPALIVE has been meet. To me
that is an unacceptable wait. 

On the Java side we had a similar issue which we solved by implementing
a thread that monitors the remote.  When ever a failure occurs, the
sockets to that device would be torn down and every N minutes new
connections would be attempted.  Maybe a similar solution could be had
in perl but it would require thread use. One thread to stream data and
one thread to verify connectivity.  I could use the timeout in the
select() in perl to do cleanup if a remote is flagged as down.

Chris
   

_______________________________________________
Ale mailing list
Ale at ale.org
http://www.ale.org/mailman/listinfo/ale