OK, if I set this up and when both establish connection the messages will
flow from one router to another, that's ok.
But what if the connection is closed?
Will it be reopened only when there is something to transfer from one
router to another?
Who is responsible for opening connections?
If I have a routers SERVER and CLIENT and CLIENT has a routing listener and
SERVER has a connection to CLIENT under connectors.
Will they be able to reopen the connection if it is closed, by an ISDN
router, ... ?
If SERVER has something to transfer to CLIENT it will be able to open the
connection to CLIENT, because it has the connection defined, right?
But what if a CLIENT wants to transfer something to SERVER and the
connection is not up? Will it be able to open it, because it does not have
a connection to SERVER defined ?
Best regards,
Kovi
At 12:00 25.5.01 +0200, you wrote:
>You define it only for the routing listener. It is handed over to the
>connector during the connect prologue phase.
>
>--
>Andreas Mueller, IIT GmbH, Bremen/Germany, http://www.iit.de
>SwiftMQ - JMS Enterprise Messaging System, http://www.swiftmq.com
>
>
>-----Original Message-----
>From: Gregor Kovač <[EMAIL PROTECTED]>
>To: <[EMAIL PROTECTED]>
>Date: Fri, 25 May 2001 12:02:34 +0200
>Subject: [developers] Keep-alive time
>
> > OK.. This is my final (I hope) question on this topic. :))
> >
> > Just to make it clear:
> > I have to set that property only on the router where I have connectors
> > defined or on both ends?
> >
> > Best regards,
> > Kovi
> >
> > At 11:50 25.5.01 +0200, you wrote:
> > > > Hmm...
> > > >
> > > > OK.. So if a routing connection on a dial-up lines is not
> > recommended,
> > > > how
> > > > can I connect the two routers together ?
> > > > Or is
> > > > setting
> > swiftlet.sys$routing.listeners.plainsocket.keepalive.interval
> > > > to 0
> > > > enough ?
> > >
> > >Sure, you can switch it simply off (sometimes I'm blind, thinking of
> > >half-open socket issues etc. instead of the simplest solutions).
> > >
> > >--
> > >Andreas Mueller, IIT GmbH, Bremen/Germany, http://www.iit.de
> > >SwiftMQ - JMS Enterprise Messaging System, http://www.swiftmq.com
> > >
> > >
> > >------------------------------------------------------
> > >SwiftMQ developers mailing list * http://www.swiftmq.com
> > >To unsubscribe from this list, send an eMail to
> > >[EMAIL PROTECTED] and write in the body of your message:
> > >UNSUBSCRIBE developers <your-email-address>
> > >Archive: http://www.mail-archive.com/developers@mail.iit.de/
> >
> >
> > ------------------------------------------------------
> > SwiftMQ developers mailing list * http://www.swiftmq.com
> > To unsubscribe from this list, send an eMail to
> > [EMAIL PROTECTED] and write in the body of your message:
> > UNSUBSCRIBE developers <your-email-address>
> > Archive: http://www.mail-archive.com/developers@mail.iit.de/
> >
> >
> >
> >
>
>
>------------------------------------------------------
>SwiftMQ developers mailing list * http://www.swiftmq.com
>To unsubscribe from this list, send an eMail to
>[EMAIL PROTECTED] and write in the body of your message:
>UNSUBSCRIBE developers <your-email-address>
>Archive: http://www.mail-archive.com/developers@mail.iit.de/
------------------------------------------------------
SwiftMQ developers mailing list * http://www.swiftmq.com
To unsubscribe from this list, send an eMail to
[EMAIL PROTECTED] and write in the body of your message:
UNSUBSCRIBE developers <your-email-address>
Archive: http://www.mail-archive.com/developers@mail.iit.de/
