Olin Lathrop <olin_piclist <at> embedinc.com> writes:
> If you want control from a program as apposed to interactively from a user,
> plain TCP would be easier than HTTP.  I would set up a TCP server in the PIC
> that accepts a binary command stream from a client.  Each command is a
> single opcode byte followed by data bytes specific to that opcode.

True, but it is always easier to use a popular protocol. In HTTP your request
would be encoded as a single line, like:

GET /%FC\r\n

And that's it (a discussion might start about how a HTTP/x.y protocol request
would be handled). It can be issued by any browser or by a telnet client for
testing. The browser address window would contain http://1.2.3.4/%FC for this.
The lowest pain method to send data over ethernet is UDP. For example ICMP
packets allow a test payload, but other protocols can be used too.

Peter


-- 
http://www.piclist.com PIC/SX FAQ & list archive
View/change your membership options at
http://mailman.mit.edu/mailman/listinfo/piclist