lwip-users
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[lwip-users] Socket API inconsistency


From: Kjell-Erik Klevan
Subject: [lwip-users] Socket API inconsistency
Date: Wed, 31 May 2006 14:48:16 +0200

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Our web server sends a lot of data xml data. 

When the size is larger than the size of an unsigned short (u16_t), the
lwip_send fails to send all data due to an inconsistency in the socket API.

The lwip_send function API uses an 'int' size while the netwconn_write uses
an 'u16_t' size.

 

int

lwip_send(int s, void *data, int size, unsigned int flags)

 

err_t

netconn_write(struct netconn *conn, void *dataptr, u16_t size, u8_t copy)

 


-----BEGIN PGP SIGNATURE-----
Version: PGP Desktop 9.0.3 (Build 2932)

iQA/AwUBRH2QmYSuEgWAxAnhEQIKAgCgvS9wGZv6/9estp8SHjf4BHN/tCYAoJQG
dDayR96iT0spubaAqzP4EojL
=w1Hy
-----END PGP SIGNATURE-----

Our web server sends a lot of data xml data.

When the size is larger than the size of an unsigned short (u16_t), the lwip_send fails to send all data due to an inconsistency in the socket API.

The lwip_send function API uses an ‘int’ size while the netwconn_write uses an ‘u16_t’ size.

 

int

lwip_send(int s, void *data, int size, unsigned int flags)

 

err_t

netconn_write(struct netconn *conn, void *dataptr, u16_t size, u8_t copy)

 

Attachment: PGPexch.htm.sig
Description: Binary data


reply via email to

[Prev in Thread] Current Thread [Next in Thread]