.NET socket, how to detect client has read

[ASB]

I have a thread which has a TcpClient. I am trying to write to it in - effectively - message mode.

I can write data to the client quite happily, but I can't figure out any way of making sure the client end has actually read the data. Any suggestions ? I'm trying to avoid sending an Ack back. Also want to keep the other end interface simple.

[AtW]

I'm trying to avoid sending an Ack back.

If you don't get Ack back then it's not reliable: tell the client how many bytes they need to expect to get, write that many bytes - wait for Ack.

Simples.

[ASB]

If you don't get Ack back then it's not reliable: tell the client how many bytes they need to expect to get, write that many bytes - wait for Ack.

Simples.

Yep, think I've got to do something like that. Poxy message framing

[AtW]

Yep, think I've got to do something like that. Poxy message framing

You are always trying to do something that goes against common practice, and that's my job!

If you are paranoid (as you should be with communications) add CRC32 to message blocks...

[lightng]

Wh nds TCP whn y'v gt UDP. S y lse a fw pckts hr nd thr. Wh crs?

[AtW]

Wh nds TCP whn y'v gt UDP. S y lse a fw pckts hr nd thr. Wh crs?

Are you posting from an iPhone?

[Weltchy]

Wh nds TCP whn y'v gt UDP. S y lse a fw pckts hr nd thr. Wh crs?

Were you playing scrabble last night and needed a few extra tiles?

[ASB]

Wh nds TCP whn y'v gt UDP. S y lse a fw pckts hr nd thr. Wh crs?

Excellent!

[NickFitz]

Wh nds TCP whn y'v gt UDP. S y lse a fw pckts hr nd thr. Wh crs?

UDP. S y lse Wh nds TCP whn y'vpckts hr nd thr gt a fw pckts hr nd thr. Wh

[Sysman]

UDP. S y lse Wh nds TCP whn y'vpckts hr nd thr gt a fw pckts hr nd thr. Wh