On Thu, 2012-07-12 at 16:46 -0700, Danny Coward wrote:
> Of the choices in mode (3), I'd probably go for option A). However, I
> do think many developers (me at least, but not Greg!) find the NIO
> APIs awkward, so can see a benefit in the simplicity of option B). The
> servlet style of specializing the Java IO APIs to allow non-blocking
> IO seems on the face of it to be overly elaborate for our needs, so I
> like option (c) least.
1) needs to be there for simple applications.
3) C is not needed here since there's no existing java.io stream API. So
3) B looks very appropriate (building the impl on top of Servlet 3.1
looks very fine).
Not convinced about 2). Worst case it can be provided as a utility on
top.
--
Remy Maucherat <rmaucher_at_redhat.com>
Red Hat Inc