My opinion on the nbio issue: I completely agree with Remy, the IO is not the issue at least for the current code and the near future. The char-byte conversions are far more expensive.
JDK1.4 provides a very nice solution for the char conversions, however my tests show it to be comparable in speed ( i.e I couldn't notice any difference ) with the current 'hack' in tomcat.util.buf ( which uses normal Writer with some recycling and other tricks ). While I would love the clean 1.4 solution, I see no particular need or benefit - so I'll not spend any time on it, but if someone contributes that - I would be +1 to add it to tomcat ( optional, if 1.4 is detected ) Regarding 'sendfile' - as part of j-t-c we'll be using a significant chunk of APR ( the apache portable runtime ) - and it would be easy to add support for sendfile as well. This will work on any platform ( where Apache can run - that's probably >= than java at least for servers ). I would rather use the APR code that is available on all VMs and provides the same feature. I'm not very sure about nbio - most of the time there's a lot of complexity ( and a different programming model, etc ) - and the benefits seems pretty small. We already spend most of the time in user code ( i.e. servlets), the container overhead is getting smaller and smaller - so improvements on this area are very unlikely to matter. But it's cool - so I'm +1 on it as long as it doesn't mess with the existing APIs ( i.e. it is implemented as a module, etc ). Costin -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
