I can't see any reason why this would not be supported going forward.

Robert


Rob Butler <[EMAIL PROTECTED]>

19/06/2006 13:44
Please respond to mina-dev

       
        To:        [email protected]
        cc:        
        Subject:        Re: server -> client async message



Thanks again Robert.

While waiting for a response I built a little test app
to do exactly what I described.  It worked for TCP and
UDP as well.  Glad to hear that it is the "correct"
way to do things for TCP at least.  Since I have
proven it does work for UDP would you consider it
"correct" for that as well, and will this remain a
"supported feature" in Mina going forward.

What I mean by that is.. I'd hate to rely on this
capability and then have new code added to Mina that
does some state checking and artificially disallows
sending messages on a UDP IoSession after the
IoHandler.messageReceived(..) message is completed.

Thanks
Rob

--- [EMAIL PROTECTED] wrote:


---------------------------------

Yes that is what you should do, certainlyin the TCP
case.

I believe it will work for UDP but Ihaven't tried
that.

Robert


Rob Butler <[EMAIL PROTECTED]>
17/06/2006 21:23
Please respond to mina-dev        
       To:       [email protected]
       cc:      
       Subject:       server -> client async message


Hello again,

I was wondering what the correct way of implementing
server to client asynchronous messaging with Mina is.

Can I place an IoSession into a global HashMap from
within a ProtocolHandler.messageReceived(...) method
and then write to the IoSession later from another
method well after the messageReceived method
completed?  This will probably work for TCP, but I
don't know if it is the correct way to do things.

Will something similar work for UDP?

Thanks again,
Rob

__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam
protection around
http://mail.yahoo.com



This communication is for informational purposes only.
It is not intended
as an offer or solicitation for the purchase or sale
of any financial
instrument or as an official confirmation of any
transaction. All market prices,
data and other information are not warranted as to
completeness or accuracy and
are subject to change without notice. Any comments or
statements made herein
do not necessarily reflect those of JPMorgan Chase &
Co., its subsidiaries
and affiliates.


__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around
http://mail.yahoo.com



This communication is for informational purposes only. It is not intended
as an offer or solicitation for the purchase or sale of any financial
instrument or as an official confirmation of any transaction. All market prices,
data and other information are not warranted as to completeness or accuracy and
are subject to change without notice. Any comments or statements made herein
do not necessarily reflect those of JPMorgan Chase & Co., its subsidiaries
and affiliates.

Reply via email to