about data packet

[Michel_Huang]

The data packets received from NIC may have Indefinite length,and among the data may include '\n','\t','\0',and so on . If I do not want to new and delete a char ** every time according to the size of data packet , are there any advanced tools or structurs can be used? Thanks for your help~

Never to say never~

[chandu004]

can you put your question more clearer?

Suggestion to the members: prefix your main thread subject with [SOLVED] if it is solved. chandu.

[led mike]

Michel_Huang wrote:

are there any advanced tools or structurs can be used?

Yes, and guess how they work? They will new and delete heap memory every time according to the size of data packet. Standard Template Library[^]

[Mike Dimmick]

If you're using UDP packets, the recv API does not allow you to read a bit of the packet then the rest of the packet. It gives you the data up to the size of the buffer you supply then discards the rest. Peeking to find out how much data is present is unreliable. You should define a maximum size packet supported and use a buffer that size. You can simply reuse the buffer once you've processed the data. The maximum packet size supported by the TCP stack can be retrieved with getsockopt, passing the SO_MAX_MSG_SIZE parameter. TCP does not preserve message boundaries. What you see at the receiver can be only part of a single call to send or it can be the result of multiple calls to send. If required, you must put some kind of framing on top of the raw data. Best practice is again to define a fixed size buffer and be prepared to handle any size of data that's returned, which can be as low as one byte. You should probably read the Winsock Programmer's FAQ[^].

---

DoEvents: Generating unexpected recursion since 1991

[Michel_Huang]

ye~ I see ,thank you ~

Work hard. Laugh often. Keep your honor. Never to say never

[Michel_Huang]

Thank you ~

Work hard. Laugh often. Keep your honor. Never to say never