Hello,
I am a bit confused as to which API I should use for communication with PC running Win7. Seems like the TCP api is more event driven whereas the BSD is the classic implementation. Does the TCP is implemented on top of the BSD sockets or they are not related at all. Do they both require RTX running The Microcontroller will run as a TCP server.
Many thanks Nick
If the protocol is TCP/IP, it really doesn't matter if you're talking to a Windows, Linux, or OSX.
>>Does the TCP is implemented on top of the BSD sockets
I'm not sure where that paradigm would make any sense, Berkeley sockets use the protocol stack, not the other way round.
Look for an example implementing an HTTP server.
Thanks, indeed I meant whether BSD utilizes the TCP API (as they can also be used for DATAGRAMS. Seems like the TCP API allows a bit more control over the communication.
What do you mean by, "TCP API" ?
TCP is a network protocol - not an API.
Your TCP/IP Stack is a piece of software that will provide an API to use it - for details, you will have to study its documentation...
I mean the TCP and BSD Network components as of here: www.keil.com/.../using_network_sockets.html My original question was if one wanted to create an application which uses TCP to communicate, which of these two APIs (tcp/bsd) would pick to use. Which library offers more flexibility/control and which programming paradigm is better. For example, from what I read the TCP is more event driven. Maybe BSD is using the TCP component and it is good enough. I am trying to read and understand the documentation but I am new in the embedded world (and ARM/Keil) and I have quickly understood that coding is different to what I am used to.
View all questions in Keil forum