>Do you know how to contact the rmi-users mailing list? I'd like to check
>them out.
Try [EMAIL PROTECTED] There's an archive at
http://archives.java.sun.com/archives/rmi-users.html
BTW, I found a cryptic reference to a property
sun.rmi.transport.connectionTimeout
that might be settable, but then again might not be standard or approved.
There's also some more relevant information at
http://developer.java.sun.com/developer/techDocs/SearchData/dd/rmi/179.html
>I guess I understand RMI's behavior since there's no such thing as a
>fixed amount of time that a method ought to execute within. It's just
>a pain when the method you call hangs up.
It's a real problem. I think this is a serious limitation in RMI; most
other distributed object systems have some sort of asynchronous
messaging capability built in. But you can work around it.
>I've been reluctant to use a thread per client (there can be hundreds
>of clients) since I'm worried about running so many threads
Sure. If you use thread pools and reuse threads, you can have a lot of
control. But that code gets tricky.
If this is a commercial system, there are commercial frameworks that
are more robust or scalable than RMI. Ask me offline, though, it's not
really appropriate to java-linux.
>Is there much experience out there with running lots of threads? I
>don't even know how well (though I could write a test program, but I
>have so much other work to do!) green threads would work in the JVM
>if I had hundreds of client push threads responding to each event.
I'd love to hear about Linux users' experiences with lots of threads,
too. Where does it break, with both green threads and native threads?
[EMAIL PROTECTED]
. . . . . . . . http://www.media.mit.edu/~nelson/
