Hi Luiz,
Luiz Hamilton R L Soares wrote:
> Hi,
>
> I'm working with Grizzly about two months. It is the core of a LBS
> Gateway here in Brazil. It is working fine and my code is very simple. I
> use
> Controller(), TCPSelectorHandler() classes and a filter, ReadFilter().
>
> Well, now I need to implement an Async Server so I can write to a client
> without a need to wait for a message. Nowadays I can send a message to a
> client only after my grizzly server receive a message from the
> client (My TCP server is working like a UDP server!!).
>
> I'm reading Grizzly ARP source code, but I can't understand how to use
> it in a TCP Server. There is an example of ARP, but it is for a HTTP
> server.
Right.
>
> Today I read an answer from Jeanfrancois Arcand in a discuss in this
> mailing list in 13 Jun 2007 where he was working with the Ericsson team
> who have requested async write to replace their NIO implementation with
> Grizzly.
Right :-) We are still discussing it (was an item on our last meeting,
which I unfortunately missed).
>
> Anyboy know if JFA generalize the implementation so it can be used
> outside of Comet?
Can you elaborate exactly on what you are looking at? With Comet, async
read and write are supported, but also the SelectionKey is parked and
later resumed when the business logic is ready. Are you looking for
something like that?
For sure I'm interested to help implementing this behavior for TCP :-)
Thanks!
-- Jeanfrancois
>
> Thanks a lot,
>
> Luiz Soares
>
> Flickr agora em português. Você clica, todo mundo vê. Saiba mais
> <http://br.rd.yahoo.com/mail/taglines/flickr/*http://www.flickr.com.br/>.
>