Greg,
The NonBlockingInptSource and NonBlockingOutputSink are no longer
present and consolidated into ServletInputStream and
ServletOutputStream. We got rid of the readers and writers so we don't
need the two interfaces anymore. dataAvailable is also not there - just
use available. We will fix this in the specification.
- Rajiv
On 05/30/2012 01:56 AM, Greg Wilkins wrote:
> The email, the javadoc and the document do not appear to match.
>
> There are no javadocs for classes called NonBlockingInputSource and
> NonBlockingOutputSink.
> NonBlockingOutputSink is mentioned only once in the the document as a
> comment to WriteListener.
> The document says that ServletInputStream should have a method called
> dataAvailable() but that is not in the javadoc (and how is that
> different to InputStream.available() ?)
>
> confused!
>
>
>
>
> On 29 May 2012 19:58, Shing Wai Chan<shing.wai.chan_at_oracle.com> wrote:
>> Hi,
>>
>> We have updated the Servlet 3.1 EDR draft.
>> The following is a summary of changes from previous draft:
>>
>> 1. removing ServletReader and ServletWriter
>> as it is hard to get the exact amount of data to be read for Readers via
>> the dataAvailable method (in the case of input) and have only the Stream
>> based APIs for non-blocking IO. Also since we are removing the Reader class
>> we also don't need the dataAvailable method. We can rely on the available()
>> method in InputStream.
>>
>> 2. renaming the AsyncIOInputSource and AsyncIOOutputSink to
>> NonBlockingInputSource and NonBlockingOutputSink
>>
>> 3. removing inputAvailable and outputReady methods in ProtocolHandler
>> as we can use non blocking IO here
>>
>> Please let us know your comments by Friday COB.
>> Thanks.
>>
>> Shing Wai Chan