When the server shuts down, does it call Socket.Shutdown or set the
LingerTime property, or do you just use Close()? Close does not
necessarily immediately close the socket; it may hang around for a
while afterwards, which would lead to the message successfully being
delivered.
On Mon, 3 Jan 200
In my class I had it turned off. I turned it off in this example too, but I
would not make a difference. I just added these lines:
// disable the Nagle algorithm
sender.SetSocketOption( SocketOptionLevel.Socket, SocketOptionName.NoDelay,
1 );
right after the connect.
Overall, it bothers me becaus
Turn off Nagle (SocketOptionName.NoDelay) on the client and see what
happens.
> -Original Message-
> From: Unmoderated discussion of advanced .NET topics.
> [mailto:[EMAIL PROTECTED] On Behalf Of Eddie Lascu
> Sent: Monday, January 03, 2005 1:51 PM
> To: ADVANCED-DOTNET@DISCUSS.DEVELOP.COM
Hello everybody and a Happy New Year 2005!
Over the Holiday vacation I created a bunch of test cases for some classes
that I wrote for Tcp/Ip network programming and I found a strange behavior.
If I have a client and a server exchanging messages and if the server
decides to go down for whatever re
Sorry, stupid outlook.
>From MSDN:
When applying the XmlIncludeAttribute, specify the Type of the derived
class. When the XmlSerializer serializes objects that include both the
base and the derived class, it can then recognize both object types.
You can use the XmlIncludeAttribute to include der
>From MSDN:
-Original Message-
From: Unmoderated discussion of advanced .NET topics.
[mailto:[EMAIL PROTECTED] On Behalf Of Martijn de
Haas
Sent: Monday, January 03, 2005 12:23 AM
To: ADVANCED-DOTNET@DISCUSS.DEVELOP.COM
Subject: Re: Using WSE to pass message objects derived from a common
