A thing to remember: TCP is a stream-based protocol. You don't have "packets" per se, so with an external server and "raw" socket mode you will have to consider that what you are reading in async event may contain more than one packet (note: no "partial" packets). Usually approached by writing the packet length into the header so that you can safely hop over to the next packet after reading one.I'm in the same boat. I have a java server that's receiving and sending fine. Just gml client losing some data (TcP) on receiving end. Ive made a queue list on the client(GML) side. Which helped i guess in regards to resending specific data.
I had that thought somewhere down in my head that would be the case lol just never thought to implement it. Thanks will try without editing to muchA thing to remember: TCP is a stream-based protocol. You don't have "packets" per se, so with an external server and "raw" socket mode you will have to consider that what you are reading in async event may contain more than one packet (note: no "partial" packets). Usually approached by writing the packet length into the header so that you can safely hop over to the next packet after reading one.
Also recommended: third three-part tutorial explaining networking fundamentals.
Hi,I'm in the same boat. I have a java server that's receiving and sending fine. Just gml client losing some data (TcP) on receiving end. Ive made a queue list on the client(GML) side. Which helped i guess in regards to resending specific data.