[EMAIL PROTECTED] wrote:
HTTP started with the idea that it would be possible to connect via
HTTP, for tunneling purposes.

I have been looking at the links and suggestions and have reached the
following conclusions:-

1) Adding general purpose web server capabilities in uSQL would be a
mistake.
2) People who allready have Webservers on the server machine would be
much better off implementing the server in PHP. The TechFell protocol
was, after all, designed to make rolling your own clients **and**
servers easy.

Agree totally with 1 & 2. Perhaps someone would be kind enough to post their PHP (or whatever) implementation sometime.

3) Each extra capability added on the network interface side
**multiplies** security risks. Any extra complications makes bugs more
likely. OTOH, looking througth the vatious minimalistic examples I have
seen that implementing basic HTTP is very simple.
So, I am going to add a very minimalistic HTTP capability that allows
you to send a query as a HTTP post and handle it with a slightly
modified reply (requests recieved via HTTP recieve replies in a HTTP
packet). This will serve as a minimum techniue and be reference for
other implementations that use e.g. HTTP. I will be modding the Cclient
so it can optionially run a query over HTTP and so that it can cope with
the new format


Agree in principle with what you're saying here as well, one suggestion - perhaps you could mod your server to accept/general queries/output via standard in/out. That way its could be piped over a multitude of channels.

Cheers - Lindsay


Reply via email to