how to convert http base program to windows application program?

"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.

"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

Thank you for all answers and discussions.
As i know ,if i use windows services, my code in windows application will be converted to
XML data and microprocessor or every system can receive it.is it possible to use windows services
and using POST and GET method like HTTP over TCP/IP?

Still rather confused about what it is exactly you want to achieve.

Is the Windows PC here acting as a client or a server?

Can you talk to your microprocessor board using a browser?

Can you use WinSock?

Windows services is just programs that run headless, i.e. without any text console or GUI interface.

So basically the same as a daemon on Unix machines.

A Windows service might encrypt file data. Or it might implement a web server (HTTP). Or it might measure and log the temperatures in the computer. Maybe listen on a RS232 or USB port or use Ethernet to interface with a UPS to issue a shutdown command to the computer in case of too long time without mains power. The sky is the limit - all you can think of that doesn't explicitly requires a visible interface to present any output on.