>>>>> On Tue, 09 Aug 2011 19:39:25 +0200, Marek Potociar <marek.potociar_at_oracle.com> said:
MP> FWIW, a colleague of mine wrote recently a nice blog post about the async HTTP processing with Grizzly 2:
MP>
http://blogs.oracle.com/oleksiys/entry/grizzly_2_0_httpserver_api1
>>>>> On Wed, 20 Jul 2011 20:49:55 +0200, Marek Potociar <marek.potociar_at_oracle.com> said:
MP> Please read through the wiki page[1] and send your thoughts to the
MP> EG list. Also, feel free to add new sections, reference links,
MP> requirements or open topics to the document, just make sure to mark
MP> the additions with your name.
MP> [1]
http://java.net/projects/jax-rs-spec/pages/AsyncServerProcessingModel
I'm sorry for my late participation. I have read [1] with a view to
maximize harmony between jax-rs and JSF. After a quick read, I don't
see any additional disharmony above what already exists between the two
jax-rs and JSF models for crafting a web application. I just have two
comments after reading [1].
MP> 3 scopes: application, URI and request.
Do we need to address tenancy requirements by adding scopes here?
MP> R002: User must be able to asynchronously locate the suspended
MP> request (connection) and resume it with a response.
How is this done? With a priori knowledge of the path with which the
request is associated?
Ed
--
| edward.burns_at_oracle.com | office: +1 407 458 0017
| homepage: | http://ridingthecrest.com/