Re: Impelementing messaging protocols (IOCP socket server)
- From: "Kürşat" <xx@xxxxxx>
- Date: Mon, 26 Nov 2007 10:29:00 +0200
I am sorry, here is the wrong group for this topic. So I open the same topic
under microsoft.public.win32.programmer.networks group.
"Kürþat" <xx@xxxxxx> wrote in message
news:uvgfTw6LIHA.4136@xxxxxxxxxxxxxxxxxxxxxxx
Hi,
I try to implement a messaging protocol in my IOCP based socket server. I
decide to use message header approach in my implementation. The header
will simply contain length of the actual message. If, for example, length
of the header is 5, first I will post a WSARecv () with a 5-byte
buffer.When this function completes, one of my IOCP workers will get the
header(i.e. length of the message body) and post another WSARecv () to get
actual message. The problem is that if a client application sends a
message with wrong header then the server gets wrong message length and
communication between the server and that client is broken (most likely
remain broken along that session). Do you have recommendations about this
issue and about building messaging protocols in general?
Thanks in advance.
.
- References:
- Prev by Date: Cpu load
- Next by Date: Re: What happens exactly when an exception happens?
- Previous by thread: Impelementing messaging protocols (IOCP socket server)
- Next by thread: BroadcastSystemMessage in VISTA
- Index(es):
Relevant Pages
|