charlie hunt wrote:
> Hi Charlie,
>
> I'm adding OpenJDK's Java SE core libraries since that's where Java NIO
> lives. I doubt anything could be done at the class libraries level since
> an API addition / enhancement would likely require JCP activity. But,
> there may be some value in raising some awareness at the class libraries
> level ?
I wouldn't expect this to necessarily be included in Java in the future;
but this port is rapidly maturing, and having such a thing available in
the community could show its value for the future.
> I'd like to hear others reactions on this mailing list. My initial
> reaction is what you are describing sounds like something that could be
> very useful for a protocol parser. The core of Grizzly is protocol
> independent. But, this might be a useful be able to offer to those who
> are implementing the com.sun.grizzly.ProtocolParser<T> interface.
> ProtocolParser is part of core Grizzly / Grizzly Framework.
Yes, this is exactly what I was thinking. The ability to do such parsing
without having to decode the incoming content could be very useful.
> I think some additional exploration / investigation is worthy. We are
> in the process of gathering new feature requests. I think we should add
> this to that list.
If you think that's a possibility. At any rate, the repository for the
Joni engine is here:
https://svn.codehaus.org/jruby/joni/src/org/joni/
The porter is Marcin Mielczynski, a member of the JRuby team, and all
credit and kudos should go his way.
- Charlie