Member Avatar for shre86

hey
i would like to know if there is anyway i can send an object or a structure directly using any winsock2 function..
its mighty difficult to convert to a string and send as required by WSASend and send functions..

  • 3 Contributors
  • 2 Replies
  • 124 Views
  • 10 Hours Discussion Span
  • Latest Post Latest Post by Dave Sinkula

Dani AI

Generated

Short answer: WSASend/send operate on raw byte buffers, so a POD struct can be sent by casting its address to char* and passing sizeof. That solves the immediate need raised by and echoed by , but it is brittle unless both endpoints share the exact same layout, packing, and endianness. See the WinSock function reference for details on the calls: WSASend and send.

Minimal example (only safe for identical environments):

struct Msg {
    uint32_t id;
    uint16_t count;
    char name[64];
};

Msg m = { ... };
int sent = send(s, (const char*)&m, sizeof(m), 0);

Key cautions and safer practices (expand on the pointers from 's pointers to online guides):

  • Do not send structs that contain pointers or non-POD members. Pointers are meaningless on the remote side.
  • Account for padding and alignment differences (use fixed-width types like uint32_t, and if needed control packing with #pragma pack on both sides) — see the compiler pack documentation: #pragma pack.
  • Convert integer fields to network byte order with htonl/htons before sending and back on receive (ntohl/ntohs): htonl.
  • Implement application-level framing: send a fixed-size header (e.g., 4-byte network-order length) then the payload, and loop on recv to accumulate the exact number of bytes (TCP is a stream; single recv may return partial data).
  • For robustness and future-proofing, use an explicit serializer or a stable format (Protocol Buffers, MessagePack, JSON, etc.); Protocol Buffers is a good production option: Protocol Buffers.

Quick troubleshooting: zero-initialize structs before sending to avoid leaking padding bytes, assert sizeof matches expected values, test between the actual sender/receiver binaries, and always handle partial sends/receives.

Recommended Answers

All 2 Replies

Member Avatar for mrlebanese

I've had this same problem :(

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.