HTTP

Hyper Text Transfer Protocol

currently the only usable network protocol with nunu

Currently there is an implementation restriction:

The protocol adaptor SHOULD, but doesn't yet, support server driven updates of the client frame. (We need that: if a place changes state, the client should reflect this. However see BOSH - maybe that's useful here.)

The user might find this a problem, cause the server delivers an older view instead of the expected state. To work around: in doubt just reload the page from you browser.

To avoid this reload step, there is KLUDGE in the HTTP protocol adaptor: the answer is artificially delayed for http-redir-kludge-time milliseconds (which appear to work only in steps of 1000). TODO remove his oddity.

Ther's only a small code change in protocol/http/server.scm. A continuation should be passed to the answer-function instead of calling it. But nevertheless it needs some coding and thinking about the handling of the change signal. It MUST be invisible to the client code. It MAY be visible to a few special places.

Here's a good description how it shoud work. http://www.xmlblaster.org/xmlBlaster/doc/http/http_tutorial.html