Hi Tomas,

> thing like the example from Alex, then the amount of work on the server
> seems rather small and avoiding sending HTTP headers seems like
> pointless micro-optimization.

True. The posts caused by the +Auto button are

   POST /55319/29110032894590418~!jsForm?!chat?*Menu=+0&*Tab=+1&*ID= HTTP/1.1
   Host: localhost
   User-Agent: Mozilla
   Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
   Accept-Language: en-us,en;q=0.5
   Accept-Encoding: gzip, deflate
   Referer: http://localhost/
   Content-Length: 51
   Content-Type: text/plain; charset=UTF-8
   Connection: keep-alive
   Pragma: no-cache
   Cache-Control: no-cache

   &*Gui:-3=Chat&*Get=1&*Form=2&*Evt=0&*Gui:1=&*Gui:2=

with a size of 449 bytes. This is less than the default TCP packet size
of 1152 bytes, so a headerless protcoll wouldn't save anything here.


> What about putting the log field into an iframe with automatic reload
> instead of the +Auto button which needs javascript?  Would that not be
> even better?

I don't know, I have never use iframes. But with them we again introduce
a new concept and new dependencies, which I try to avoid.

The +Auto button is more general, and I use it quite often.

♪♫ Alex
-- 
UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe

Reply via email to