>If I remember correctly http goes both ways. Also its not really a lot
>of baggage - you can f.i. structure your plugin stuff in the filesystem
>tree, so a GET parameters/factor[.html] would just get you a "1.233"
>f.i., and PUT (or was it PUSH?) of the same sort sets the value.
>Note again, using an existing protocol helps development and debugging
>and probably interoperability.
actually, i can tell you from experience that it doesn't. there are 2
reasons:
1) HTTP is stateless
this has been widely criticized, and widely praised.
its already apparent that the LCP protocol cannot
be stateless
2) the hard part of handling protocols is not implementing
formatting, delivery + parsing of messages. its
integrating the handling of i/o into the structure
of the client+server. no HTTP library that i've seen
will help with that. in fact, no protocol library
of any kind that i've seen helps with that.
>Anyone knows another simple standard protocol that can be used?
i don't understand. why do you want to use a generic, essentially
complex protocol to replace a specific, extremely simple one?
--p
