Hi all I developed a HTTP base control program on a cortex m3 microprocessor and i would like to do the same with a windows application .which protocol i have to use instead of http?Can you give me some guide how to do it?is there any sample example?
Thanks
What does this have to do with Keil tools or products?
http://www.keil.com/forum/
Surely, you need to be asking on a Windows developer forum?!
eg, http://msdn.microsoft.com
But what makes you think that Windows can't understand HTTP?!
I have not written a program on an arm yet for ethernet communications. Other choices besides HTTP would be TCP IP or UDP. MSDN has example programs on how to write TCP or UDP C++ or C Sharp programs. One way to set up the Microcontroller board for this type of communications is if you can set up a LWIP program in TCP or UDP mode.
If he's using HTTP already, then he's almost certainly doing it over TCP/IP ...
"Other choices besides HTTP would be TCP/IP..."
Note that HTTP is a carrier-independant protocol, that doesn't care about how messages are sent or how you managed to address the other side.
While TCP/IP is a more-or-less carrier-specific protocol operating at a much lower level, and intended to be used with other protocols on top.
So you can do HTTP communication over TCP/IP. Or over RS232. Or potentially over a pidgin relay link, if you can survive the latencies.
I must say I don't know what a "HTTP base control program" is.
But HTTP is probably the most used protocol in the world right now for interfacing systems and pushing/requesting messages between applications.
While "the public" most often see HTTP used with HTML for distributing web pages, it is very often used with JSON, SOAP (XML) and quite a number of other protocols to encode the actual messages while HTTP is used to handle the actual transfers and to acknowledge requests.
And the advantage with such a massively used protocol is that a web browser, wget, cURL or similar can be used when testing.
Indeed - which is why I said, "almost certainly doing it over TCP/IP"
"potentially over a pidgin relay link, if you can survive the latencies."
eg, RFC 2549: tools.ietf.org/.../rfc2549
;-)
" advantage with such a massively used protocol is that a web browser, wget, cURL or similar can be used when testing"
And it is not tied to any particular platform - such as Windows, ARM microcontroller, or whatever.
Yes, RFC 2549 is for people with a bit higher demands.
But there's always the possibility of going for the 9 year older, but simpler, RFC 1149, if quality-of-service (QoS) isn't needed.
www.ietf.org/.../rfc1149.txt
View all questions in Keil forum