HTTP/1.1 200 OK Date: Sun, 12 Feb 2012 23:49:39 GMT Server: Apache/2.2.6 (Fedora) Last-Modified: Tue, 11 Apr 1995 08:21:22 GMT ETag: "73cc6-6f8-a258480" Accept-Ranges: bytes Content-Length: 1784 Connection: close Content-Type: text/html; charset=UTF-8

Session protocols (client-server or peer-to-peer)

Reasons PRO

More efficient than server-to-client callbacks for fine-grained symmetric interaction.

Reasons CON

Requires stateful server (although impact can be regulated by factoring out the stateful part of the server, as in Ubique's proposal).

Applications

Conferencing, `chat rooms'.
Control of cameras, robot devices, and other apparatus.

Proposed Solutions

HTTP-NG Session Control Protocol (server-client) - Simon Spero (EIT)
``Server Push'' (server-client) - Netscape
Shared Mosaic (peer-to-peer) - Vinay Kumar (EIT)
Virtual Places Protocol (both client-server and peer-to-peer; proprietary?) - Ubique

Updated: Tue Apr 11 1995
Up to Enhanced communication model.
Home to Interactive Standards Home Page.

HyperNews Responses

1. Another Client-Server protocol (Andrew Pam)