The asyncweb API is quite different from this approach - and is much less "servletty". Maybe take a look at the API and see what you think? All the Java docs are contained in the current release available here:
https://svn.safehaus.org/repos/asyncweb/release/ Dave > -----Original Message----- > From: Remy Maucherat [mailto:[EMAIL PROTECTED] > Sent: 20 May 2006 00:38 > To: Tomcat Developers List > Subject: Re: Greg Wilkins' blog on async servlet API > > Costin Manolache wrote: > > I agree, it's not very intuitive - but it's still good to > understand > > it, and maybe learn from what we like and don't like it :-) > It's hard > > to make something simple, intuitive, easy to implement, high > > performance, flexible - all at the same time. > > The javadoc seems quite explicit: you may send the response > later (when the "notify" method is called). It's not much > (and what is this "key" > class all about ??; personally, I also started with an object > as an id, but yanked it as it was useless). > > Rémy > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] For > additional commands, e-mail: [EMAIL PROTECTED] > > This e-mail and any attachment is for authorised use by the intended recipient(s) only. It may contain proprietary material, confidential information and/or be subject to legal privilege. It should not be copied, disclosed to, retained or used by, any other party. If you are not an intended recipient then please promptly delete this e-mail and any attachment and all copies and inform the sender. Thank you. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
