On Thursday, May 24, 2001, at 10:10 AM, Todd Bradley wrote:
I definitely like where you're headed with this. As someone else pointed
out, Jabber needs much more explanatory errors. Right now, the client knows
nothing about the reason for why it was disconnected from the server.
In general the
That's how the
new version of Gabber works now, I'm told (though I haven't tried it
myself).
Todd.
-Original Message-
From: Jens Alfke [mailto:[EMAIL PROTECTED]]
Sent: Thursday, May 24, 2001 10:26 AM
To: [EMAIL PROTECTED]
Subject: Re: [JDEV] Multiple logins
IMHO, if a c
Title: RE: [JDEV] Multiple logins
I must
agree with Jens on this one, or at least partly: I think
clients need to auto-reconnect (at the user's preference), but
the libraries that clients are built on top of should
NOT attempt an auto-reconnect. Let the client code handle
an
;
>>For me at least, it would be nice to just get the "reason" for the problem,
>>though.
>>
>>Matt
>>
>>-Original Message-
>>From: Robert Temple [mailto:[EMAIL PROTECTED]]
>>Sent: Wednesday, May 23, 2001 1:31 PM
>>To: '[EMAIL PR
IMHO, if a client is disconnected by the server [receives an and ] it should not automatically attempt to reconnect. There is probably some good reason it was disconnected, and this thread illustrates one of the dangers of automatic reconnects. It'd be better to put up a dialog box with "Reconnect
hough.
>
> Matt
>
> -Original Message-
> From: Robert Temple [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, May 23, 2001 1:31 PM
> To: '[EMAIL PROTECTED]'
> Subject: RE: [JDEV] Multiple logins
>
> The server handles this strangely. All it
me at least, it would be nice to just get the "reason" for the problem,
though.
Matt
-Original Message-
From: Robert Temple [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, May 23, 2001 1:31 PM
To: '[EMAIL PROTECTED]'
Subject: RE: [JDEV] Multiple logins
The server handle
The server handles this strangely. All it sends to the client
that is being disconnected is this:
Disconnected
I suspect that Jarl just automatically tries to reconnect when
it gets disconnected for some unknown reason. If the server made
it known that the reason a client was disconnected was
Yea, that's exactly what happens. I guess I'll have to deny that second
connection somehow. Thanks.
Tony
Max Horn <[EMAIL PROTECTED]> wrote:
> At 14:41 Uhr -0400 23.05.2001, Tony Byers wrote:
> >I noticed by accident that if I log into my server with the same username
> >and resource twi
This has been the behaviour I've seen since the days of 1.0.
I think what happens is that the new connection clobbers the old
one as expected, but most client do this automagic reconnect thing
after a certain time period, so you end end with this flipping back and
forth between the two clients.
-
At 14:41 Uhr -0400 23.05.2001, Tony Byers wrote:
>I noticed by accident that if I log into my server with the same username
>and resource twice at the same time, both instances disconnect and reconnect
>continuously. I'm using Jarl and jabber 1.4.1. Has anyone else seen
>this behavior? Also is
11 matches
Mail list logo
