Re: Socket Send and Receive Thread Safety
From: Ivar (ivx_at_lumisoft.ee)
Date: 02/21/05
- Next message: Mary Chipman [MSFT]: "Re: Assume SQL Server Rights for apps, any cons?"
- Previous message: pmattson: "The memory could not be "read""
- In reply to: Nizar: "Socket Send and Receive Thread Safety"
- Next in thread: Nizar: "Re: Socket Send and Receive Thread Safety"
- Reply: Nizar: "Re: Socket Send and Receive Thread Safety"
- Messages sorted by: [ date ] [ thread ]
Date: Mon, 21 Feb 2005 20:16:48 +0200
Hi,
Just think about it:
You can do it, it's not leagal but how you gurantee that data is sent to
socket in right order ?
For example:
you need to send:
aaaaaa
bbbbb
You call aaaaaa from 1 thread and bbbbbb on another:
what may happen:
aaaaaa
bbbbb
----- all as you excpect
bbbbb
aaaaa
This may happen if bbbbb thread finishes first.
For recieve, you never can be sure what is recieved by one thread and
another.
may happen following situation:
aaaaabbb
bbbb
"Nizar" <Nizar@discussions.microsoft.com> wrote in message
news:E365972C-6186-4705-A734-E285B073FE30@microsoft.com...
> Is it safe for one thread to call Socket.Receive and another to call
> Socket.Send on the same Socket at the same time?
>
> The documentation says that instance members are not guaranteed to be
> thread
> safe, but I'm not sure whether this combination is or not.
>
> I've also heard that the send and receive buffers are disparate and can be
> accessed simultaneously.
- Next message: Mary Chipman [MSFT]: "Re: Assume SQL Server Rights for apps, any cons?"
- Previous message: pmattson: "The memory could not be "read""
- In reply to: Nizar: "Socket Send and Receive Thread Safety"
- Next in thread: Nizar: "Re: Socket Send and Receive Thread Safety"
- Reply: Nizar: "Re: Socket Send and Receive Thread Safety"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|