Re: [lwip-users] Selecting correct lwIP API

[Noam weissman]

Hi,

I am working with LwIP for more than two years now. I am only working in RAW 
mode.

As far as I see people that work in embedded use either RAW or netconn. BSD 
simply takes 
more resources.

What STM32 do you intend to use ?

BR,
Noam.

-----Original Message-----
From: address@hidden [mailto:address@hidden On Behalf Of ella
Sent: ב 04 נובמבר 2013 08:29
To: address@hidden
Subject: [lwip-users] Selecting correct lwIP API

Hi,
My goal is to write a server running on my STM32 board with FreeRTOS.
Connection to the server should be done via TCP/IP socket from a number of 
clients (up to 10) running BSD socket on Linux/Windows PC.

I'm trying to understand what API is better for me. And especially principal 
difference between netconn and socket API. I worked a lot with socket on Linux 
and Windows so I'm familiar with TCP and UDP sockets. But from the other side I 
do not care about portability of the server side code as it will run only under 
lwIP. 

>From what I could understand netconn should be more efficient but less 
>portable (Am I right?). 
But I'm not quite sure if this is the right way to run server with netconn and 
clients with BSD sockets?
Besides I'm not quite sure about props and corns of both. Can you please help 
me to choose the right API.
Thanks.





--
View this message in context: 
http://lwip.100.n7.nabble.com/Selecting-correct-lwIP-API-tp22026.html
Sent from the lwip-users mailing list archive at Nabble.com.

_______________________________________________
lwip-users mailing list
address@hidden
https://lists.nongnu.org/mailman/listinfo/lwip-users

 
 
************************************************************************************
This footnote confirms that this email message has been scanned by PineApp 
Mail-SeCure for the presence of malicious code, vandals & computer viruses.
************************************************************************************






************************************************************************************
This footnote confirms that this email message has been scanned by
PineApp Mail-SeCure for the presence of malicious code, vandals & computer 
viruses.
************************************************************************************