Return-Path: Delivered-To: apmail-jakarta-tomcat-user-archive@apache.org Received: (qmail 7169 invoked from network); 26 Jun 2002 08:15:55 -0000 Received: from unknown (HELO nagoya.betaversion.org) (192.18.49.131) by 209.66.108.5 with SMTP; 26 Jun 2002 08:15:55 -0000 Received: (qmail 17707 invoked by uid 97); 26 Jun 2002 08:15:41 -0000 Delivered-To: qmlist-jakarta-archive-tomcat-user@jakarta.apache.org Received: (qmail 17691 invoked by uid 97); 26 Jun 2002 08:15:40 -0000 Mailing-List: contact tomcat-user-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Tomcat Users List" Reply-To: "Tomcat Users List" Delivered-To: mailing list tomcat-user@jakarta.apache.org Received: (qmail 17679 invoked by uid 98); 26 Jun 2002 08:15:40 -0000 X-Antivirus: nagoya (v4198 created Apr 24 2002) Message-ID: <00db01c21cea$1e0cb730$0a14a8c0@terre> From: "Chris Brown" To: "Tomcat Users List" References: Subject: Re: Repost: Java 1.4 io classes Date: Wed, 26 Jun 2002 10:18:57 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2600.0000 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 X-Spam-Rating: 209.66.108.5 1.6.2 0/1000/N X-Spam-Rating: 209.66.108.5 1.6.2 0/1000/N Apparently, it's not very applicable, because current servlet APIs require one thread per request. As I understand it, the only real way the new I/O APIs can be used at present is internally by the servlet engine to receive requests, which are then passed onto a specific thread and servlet. As someone who uses creates servlets, as opposed to servlet engines, you won't see any real difference. I've heard rumours that the next version of the servlet spec will try to make use of these APIs, but the spec isn't public yet (although this should change soon). - Chris B ----- Original Message ----- From: To: Sent: Tuesday, June 25, 2002 6:52 PM Subject: Repost: Java 1.4 io classes > Okay, I'll give this question one more shot..., then I'll assume the answer > is "No"..... > > I am wondering if Tomcat soon will make (or already has made) use of new io > classes in Java 1.4 such as java.nio.channels.SelectableChannel? Supposedly > all this gives you non-blocking i/o that will be much more scalable than > old thread-oriented blocking i/o, but I dunno if it's truly applicable to > servlets. Can anybody shed some light on this? > > > > -- > To unsubscribe, e-mail: > For additional commands, e-mail: > > > -- To unsubscribe, e-mail: For additional commands, e-mail: