Thank you all for you good advices.
I think the SO_KEEPALIVE is THE thing I was looking for! Thanks Ger:).
Do not worry I will make sure I read enough about it:).
Thanks again.
On Fri, Nov 7, 2008 at 5:23 PM, Ger Hobbelt <[EMAIL PROTECTED]> wrote:
> First of all: heed David's [Schwartz] advice
First of all: heed David's [Schwartz] advice, especially in his last email.
This stuff is /not/ meant to fix broken designs but only to be used
when you absolutely have to:
what you can use, when you need to detect clients crashing or networks
failing, is add a 'heartbeat' (as was mentioned befo
> Thank you again David,
You are welcome.
> As for the network issue scenarios here are some details about the last
case:
> 1)The server is running on UNIX, the client is running on windows or unix.
> unplug the client or the server. The server does not report anything!
Logical, nothing has h
AIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Md Lazreg
Sent: Wednesday, November 05, 2008 03:50
To: openssl-users@openssl.org
Subject: Re: client crash or network issue?
Thank you again David,
It seems that now I understand all the crash scenarios and my server can
deal with them c
Thank you again David,
It seems that now I understand all the crash scenarios and my server can
deal with them correctly. Thank you for your guidance.
As for the network issue scenarios here are some details about the last
case:
1)The server is running on UNIX, the client is running on windows o
> Thanks David.
> Unfortunately option 1) and 3) are not possible for my clients.
In other words, you cannot engineer a sensible option and have to fake it.
That's fine, but solutions that aren't engineered tend to be poor.
> option 2) seems the way to go for me, but so far it proved unreliable
Thanks David.
Unfortunately option 1) and 3) are not possible for my clients.
option 2) seems the way to go for me, but so far it proved unreliable. Here
are some scenarios I have been playing with:
1)Crash a client running on unix:
The SSL_read returns 0 . The SSL error code is SSL_ERROR_SYSCA
Md Lazreg wrote:
> Actually the same question is valid even if I am not using SSL sockets.
> So is there a way to distinguish between if a socket was closed because
> of a client crash or because of a netwrok issue?. If yes, is there an
> equivalent under SSL sockets?
You have three choices:
1)
Actually the same question is valid even if I am not using SSL sockets. So
is there a way to distinguish between if a socket was closed because of a
client crash or because of a netwrok issue?. If yes, is there an equivalent
under SSL sockets?
Thanks
On Wed, Oct 29, 2008 at 2:09 PM, Md Lazreg <[E
