mina-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Maarten Bosteels" <mbosteels....@gmail.com>
Subject Re: Synchronous calls with IOConnectors
Date Sat, 03 May 2008 18:02:24 GMT
Hi,

Have a look at the RequestResponseFilter:
http://mina.apache.org/report/trunk/apidocs/org/apache/mina/filter/reqres/RequestResponseFilter.html

Maarten

On Sat, May 3, 2008 at 1:43 AM, Daniel Wirtz <daniel@virtunity.com> wrote:

> Afaik you can also let the Future objects (ConnectFuture on
> connector.connect(), WriteFuture on session.write() etc.) await() the
> desired events in a blocking manner. Of course this will need a thread for
> each connection as in good ol' threading times so that there is no
> advantage
> from nio anymore.
>
> regards
> Daniel
> On Fri, May 2, 2008 at 6:56 PM, Jose Maria Alvarez Fernandez <
> jmalvarezf@gmail.com> wrote:
>
> > You could use the statemachine to maintain the session state and know
> what
> > to
> > do when a message comes, in case you would like to try MINA 2.
> >
> > If not, you could use an object as a parameter in the session to know
> what
> > to
> > answer, or to know that the response is the answer to a question
> > previously
> > sent.
> >
> > Hope it helps!
> >
> > Chema
> > El Friday 02 May 2008 17:51:43 Abhijit Bhatode escribió:
> >  > Hi,
> > >
> > > I am writing a client using IOConnector. The client sends a message to
> > > server and expects a response message. Is there any way to achieve
> this
> > > synchronous form of communication with MINA? Or do I need to implement
> > this
> > > explicitly by some sort of thread notification.
> > >
> > > Thanks,
> > > Abhijit
> > >
> > >
> > >
> > >
> > > DISCLAIMER
> > > ==========
> > > This e-mail may contain privileged and confidential information which
> is
> > > the property of Persistent Systems Ltd. It is intended only for the
> use
> > of
> > > the individual or entity to which it is addressed. If you are not the
> > > intended recipient, you are not authorized to read, retain, copy,
> print,
> > > distribute or use this message. If you have received this
> communication
> > in
> > > error, please notify the sender and delete all copies of this message.
> > > Persistent Systems Ltd. does not accept any liability for virus
> infected
> > > mails.
> >
> >
> >
>
Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message