Hi Jan and Judy,
Great thanks both of you.
Thankfully, I could savvy the status of the "Servlet3.0", and what I should
do next.
To Jan
> I wanted to follow up with you and let you know that the upcoming
> nightly build will provide a feature-complete implementation of the
> Servlet 3.0 APIs.
->This sound feels is good to me! I'm looking forward to release the latest
build of GlassFish-web-ea.
> There have been a few changes to the async APIs since you last looked at
> them. Most notably, the javax.servlet.AsyncContext#forward methods
> have been renamed to AsyncContext#dispatch, and a new ASYNC request
> dispatcher type has been added to identify any requests that have been
> dispatched using this API.
->I got it. I will change my code.
> Only filters that have been declared to support the ASYNC dispatcher type
> will be considered during an ASYNC dispatch. A filter that has been
> configured for ASYNC and other types of dispatches (e.g., FORWARD) may
> query the request for its current dispatcher type (by calling the new
> ServletRequest#getDispatcherType), and act accordingly.
->唯一 ASYNC リクエストディスパッチャータイプをサポートする為に、宣言されるフィルターのみが、 ASYNC
がディスパッチしている間、凝視されます。 ASYNC と他いくつかのディパッチャータイプ (e.g., FORWARD)
向けに設定されたフィルターは、その、現在のディスパッチャータイプ ( 新しい ServletRequest#getDispatcherType
を呼び出すことによって ) 向けに、リクエストを問い合わせるとともに、それに応じて動作します。
> I should point out that there is one outstanding issue that the
> Servlet EG is trying to close on: the semantics of a zero-argument
> AsyncContext#dispatch. While our impl will perform an ASYNC dispatch
> of the request and response to the current request URI (as returned by
> HttpServletRequest#getRequestURI), which corresponds to the target of
> the most recent FORWARD dispatch (or the original URI if no FORWARD
> dispatches have occurred), some Servlet EG members have been
> arguing that an ASYNC dispatch should always go to the original
> URI. Hopefully, we'll be able to agree on the semantics soon within the
> Servlet EG.
->Oh great ! Now I savvy that you are so hard to work.
> For now, you have to rely on the javax.servlet.ServletRequest and
> javax.servlet.AsycContext javadocs for documentation of the latest
> async features, but we will follow up with blogs in the near future.
->Aye,aye. I started to leraning more deeply about this, thanks!
> Please give our impl a try and let us know if you run into any
> problems.
->My pleasure !
To Judy
> I can already see a big smile on Jack's face.
->Why do you savvy the character of me ? (@_@)?
--
Always Thanks
Jack