"Attila Szegedi" <[EMAIL PROTECTED]> writes: > Well I didn't want to bring this to the sunlight so soon but since > you brought up the issue: I'm developing a generic non-blocking > server framework for JDK 1.4. > > It handles all subtleties of the non-blocking server's life, such as > non-blocking pipes for servlet output buffering, thread scaling > (since a single selector handles at most 63 channels, you still need > multiple threads), channel registration from a different thread than > the thread that listens to the selector via a mechanism similar to > Swing's invokeAndWait(), etc, etc. Using this framework, all you > need to do is implement a single ProtocolHandler interface and focus > your attention on the protocol implementation and not on the details > of non-blocking I/O.
Have you looked at Matt Welsh's SEDA <http://www.cs.berkeley.edu/~mdw/proj/sandstorm/>? -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
