When to immigrate from jetty 5.1 to 6.x

Poster	Content
dongliu nk4um User Posts: 8	<div>I think it is worth trying the NIO of jetty 6 now, since NIO is already the first choice of jetty 6. NIO was just for testing in jetty 5 days. <br/><br/>Something interesting that I will also look into is comet. <br/><br/>Cheers,<br/><br/>Dong </div> 2007-11-08T22:10:05.000ZNovember 8, 2007 22:10 I think it is worth trying the NIO of jetty 6 now, since NIO is already the first choice of jetty 6. NIO was just for testing in jetty 5 days. Something interesting that I will also look into is comet. Cheers, Dong
tab nk4um Moderator Posts: 485	<div>Yes the difference in using NIO will be interesting. We were going to do that work but then the folks at Jetty said that they didn''t rate NIO so we didn''t bother. This was a couple of years ago I believe so things may have changed.<br/><br/>When you get Jetty working with NIO take a look at the asynchronous NKF request API in NetKernel - i.e. issueAsyncRequest() rather than issueRequest() this will ensure that you don''t tie up any handling thread on the transport side.<br/><br/>To answer your question about the thread pools: NetKernel has it''s own scheduler thread pool. All requests are executed by threads in that pool. Jetty running without NIO has it''s own thread pool. When a request comes in, the Jetty HTTP transport passes it through the request throttle and it is then placed into the execution queue of the kernel.<br/><br/>Cheers,<br/>Tony</div> 2007-11-08T08:20:44.000ZNovember 8, 2007 08:20NIO Yes the difference in using NIO will be interesting. We were going to do that work but then the folks at Jetty said that they didn''t rate NIO so we didn''t bother. This was a couple of years ago I believe so things may have changed. When you get Jetty working with NIO take a look at the asynchronous NKF request API in NetKernel - i.e. issueAsyncRequest() rather than issueRequest() this will ensure that you don''t tie up any handling thread on the transport side. To answer your question about the thread pools: NetKernel has it''s own scheduler thread pool. All requests are executed by threads in that pool. Jetty running without NIO has it''s own thread pool. When a request comes in, the Jetty HTTP transport passes it through the request throttle and it is then placed into the execution queue of the kernel. Cheers, Tony
dongliu nk4um User Posts: 8	<div>The stuff I want to try is NIO of jetty 6. I want to check if there will be significant performance improvement over blocking io used in jetty 5. <br/><br/>Another thing I want ask you is about the thread pool of jetty. To my understanding, netkernel has its own threading handling facility, and does not rely on that of jetty''s. Although threading is configured in etc/TransportJettyConfig.xml, it does not do the job. Am I correct? <br/><br/>Cheers,<br/><br/>Dong </div> 2007-11-07T22:24:09.000ZNovember 7, 2007 22:24 The stuff I want to try is NIO of jetty 6. I want to check if there will be significant performance improvement over blocking io used in jetty 5. Another thing I want ask you is about the thread pool of jetty. To my understanding, netkernel has its own threading handling facility, and does not rely on that of jetty''s. Although threading is configured in etc/TransportJettyConfig.xml, it does not do the job. Am I correct? Cheers, Dong
tab nk4um Moderator Posts: 485	<div>Hi Dong and welcome to the forum,<br/><br/>yes it might be a good idea to move to a later version of Jetty. We have seen no push for this either from users or from our own requirements yet. However if you''d like to see it then that is great. What features are you looking to gain from upgrading?<br/><br/>As far as the source for the bootloader, you are right it isn''t shipped and that is an oversight on 1060''s part. I''ll get the source uploaded to a server and send you a link. However if you want to play with different versions of Jetty that is in the http module and should need to touch the bootloader,<br/><br/>Cheers,<br/>Tony</div> 2007-11-07T08:12:33.000ZNovember 7, 2007 08:12 Hi Dong and welcome to the forum, yes it might be a good idea to move to a later version of Jetty. We have seen no push for this either from users or from our own requirements yet. However if you''d like to see it then that is great. What features are you looking to gain from upgrading? As far as the source for the bootloader, you are right it isn''t shipped and that is an oversight on 1060''s part. I''ll get the source uploaded to a server and send you a link. However if you want to play with different versions of Jetty that is in the http module and should need to touch the bootloader, Cheers, Tony
dongliu nk4um User Posts: 8	<div>Hi, <br/><br/>I find the latest release 3.3 is still based on jetty 5.1. I wonder if it is planned to immigrate to jetty 6. And how difficult would that be? <br/><br/>I want to experiment first, but could not find the code for BootLoader. <br/><br/>Cheers,<br/><br/>Dong</div> 2007-11-07T04:32:01.000ZNovember 7, 2007 04:32When to immigrate from jetty 5.1 to 6.x Hi, I find the latest release 3.3 is still based on jetty 5.1. I wonder if it is planned to immigrate to jetty 6. And how difficult would that be? I want to experiment first, but could not find the code for BootLoader. Cheers, Dong

nk4um

When to immigrate from jetty 5.1 to 6.x