I forgot one lately added agenda item, (issue 38, OutputWriter can't
handle multiple writers).
Synchronization of multiple writer threads attempting to write the same
underlying SocketChannel is required to be done upstream of the
OutputWriter. At the moment, know protocols implemented on top of
grizzly are doing this synchronization, (i.e. at the protocol level
rather than transport level).
Jeanfrancois had initially thought he had this implemented for the SIP
server. But, upon re-checking it was not done and added it to the SIP
server.
Additionally, Harsha took an action item to file a RFE to create a
"MultiplexedOutputWriter" which would support the synchronization of
multiple threads writing to the same underlying SocketChannel.
charlie ...
charlie hunt wrote:
>> Agenda:
>> 1.) GlassFish ORB / Grizzly Integration progress (Harsha)
>
> - Harsha has glassfish orb unit test cases passing.
> - Integration currently does not use Grizzly's connection management.
> - Observing and investigating some performance concerns compared to
> GlassFish ORB's prior implementation.
> - Review of what's been integrated will begin shortly.
>> 2.) UDP Servers (Alexey)
> There may be some design & implementation issues with the use of
> SelectionKey attachments and the use of Context with datagrams.
> Alexey is actively working with Radim on this core issues, (thanks
> Radim for your help and contribution!).
>> 3.) Collection of new feature requests (Jeanfrancois)
> Jeanfrancois asking java.net to make a wiki available for us where we
> put the new feature requests.
>> 4.) Addl performance test (add Grizzly transport to encode
>> benchmark) (Charlie)
> No progress on this task.
>
> charlie ...