gregw

« Push vs Pull | Main | Comet Performance »
Sunday Jul 22, 2007

Async Servlet 3.0 Proposal

A recently blogged about my thoughts on the JSR-315 Asynchronous servlet 3.0 concerns. I have now worked those thoughts into a proposal that I have submitted to the expert group.

This proposal is clearly influenced by Jetty Continuations in that it allows requests handling to be suspended and resumed.  However it avoids the contentious RetryException thrown by Jetty.

This proposal also goes beyond continuations by including an extensible mechanism for containers to handle content on behalf of the servlets. This will allow containers to use the most efficient IO and reduce the complexity that a servlet developer needs to contend with in an asynchronous world.

Posted at 09:51AM Jul 22, 2007 by gregw in General  |  Comments[1]

Comments:

Greg: Would it make any sense to store the continuation in an object DBMS linked into the application server that was maintaining an in-memory cache of the database contents (and thus also of continuation data structures). The DBMS would insure that updates and additions (e.g., the data structures representing the continuations) were written to 'stable storage' before returning to the caller. Special smart delete operations would allow deletion of the data structures associated with no-longer needed continuations efficiently.

Posted by Thomas Atwood on August 09, 2007 at 05:29 AM EST #

Post a Comment:
  • HTML Syntax: Allowed

Webtide

Webtide Logo

Calendar

« October 2008
MonTueWedThuFriSatSun
  
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
  
       
Today

Tags

3.0   ajax   api   async   asynchronous   bayeux   comet   cometd   continuation   dojo   easerver   google   http   io   j2ee   java   jcp   jee   jetty   jsr154   junit   netcraft   push   richweb   server   servlet   servlet3.0   servlets   test   tomcat  

Search

Links

Navigation

Referrers