Hi Oleg, > I have the first version of an ultra trivial asynchronous I/O event > dispatcher ready. My implementation is largely based on the I/O Reactor > pattern of Doug Lea. The I/O dispatcher does not do much at the moment > but I already have a runnable version of an echo server based on it. > Surprisingly, that takes very little code.
So I take it that NIO is advantageous primarily on the server side. That solves a few of the tihings that have puzzled me so far about HttpNIO. > Is anyone interested in seeing the intermediate results of my work and > giving my an early feedback? Shall I start committing code early, or > shall I hold off until the whole HTTP transport is more or less ready > and the API is more or less feature complete? I won't be able to give you feedback on NIO, since I don't have the time or inclination to learn enough about NIO in the near future. Regarding source repositories, I usually check in as soon as stuff compiles. In this case I'm wary because of the pending changes with the connections. On the other hand, code will have to be adapted whether it's in the repository or not. So go ahead an commit the new stuff if you want to. cheers, Roland --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
