[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [GNU Crypto] exception on multiple SaslConnection.send() calls
From: |
Bryan Hoover |
Subject: |
Re: [GNU Crypto] exception on multiple SaslConnection.send() calls |
Date: |
Wed, 08 Dec 2004 19:50:57 -0500 |
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Jim Basney wrote:
> Bryan Hoover <address@hidden> wrote:
> > Jim Basney wrote:
> > > Am I doing something wrong?
> >
> > Don't comment the reconnect call :). If possible, the existing connection
> > will be reused,
> > so "reconnect" is in a sense, a bit of a misnomer.
>
> Hmmm. SaslConnection.reconnect() calls disconnect() then connect(),
> which creates a new Socket(). Watching the network with ngrep, I see a
> new TCP socket connection after the SaslConnection.reconnect() call.
Well, statelessness protocals, and all that you know.
But the security session -- that's the time consuming thing you want to reuse
if possible, and
that what the lib does, unless, for instance, it's been to long, and session
timed out. Then
you have to renogotiate the security layer -- basically start all over like a
first time
connection.
Bryan
_______________________________________________
> gnu-crypto-discuss mailing list
> address@hidden
> http://lists.gnu.org/mailman/listinfo/gnu-crypto-discuss
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (MingW32) - GPGrelay v0.955
iD8DBQFBt6Fy38ZFbCo67y4RAjXsAJ99xIPsddpbeJDnU3VGP845WsmD3QCfUUT1
FNK9CuyNKooUweSoTLoM+3k=
=vQd8
-----END PGP SIGNATURE-----
Re: [GNU Crypto] exception on multiple SaslConnection.send() calls, Bryan Hoover, 2004/12/08