|Subject:||HTTPServer or just a TCPServer|
|Posted by:||Rene Tschaggelar (no…@none.net)|
|Date:||Wed, 14 Mar 2007|
Upon a closer look at the subject I found the
HTTPServer to be a ill suited construct.
For some historic reasons, the HTTP commands are
sent as TCP commands, but contrary to the usual
TCP interactions, HTTP is connectionless.
I should route HTTP commands from a browser to
a device connected to the serial port. The serial
port is connected as nonblocking.
The HTTP server is blocking. This means to connect
the two, I'll need a separate thread.
Or would the whole become simpler If I started
with a TCP Server ?