danch wrote:
I mean, a JVM could also (try to) multiplex sockets under the covers, reusing one 'physical' socket for all communications between our process and any IP:Port pair. If, say, the Kaffe VM had that feature, would you say that we don't have to worry about system limits on sockets?Sacha Labourey wrote:The Object pooling question was definately settled on the side of it's not worth it, but things like threads and sockets _are_ different in that the underlying OS has its own limits and imposes them on us.
maybe for sockets, but not for threads: a JVM could have (and JRockit does)
an abstraction layer between OS-threads and JVM-threads and do its own
scheduling.
Yeah, a JVM could have, and one does. That's hardly enough to let us assume that it's pervasive.
-------------------------------------------------------
This SF.NET email is sponsored by: Thawte.com
Understand how to protect your customers personal information by implementing
SSL on your Apache Web Server. Click here to get our FREE Thawte Apache Guide: http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0029en
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
