W3C home > Mailing lists > Public > w3c-wai-ig@w3.org > January to March 2001

Re: Accessible chat software

From: David Woolley <david@djwhome.demon.co.uk>
Date: Sun, 4 Feb 2001 10:45:42 +0000 (GMT)
Message-Id: <200102041045.f14Ajgv27464@djwhome.demon.co.uk>
To: w3c-wai-ig@w3.org
> 
> I am trying to find an accessible chat program to install on a site I am
> working on. I have found some that are perl-base (and therefore tweakable),
> but all seem to be dependent on meta-refresh.

They would have to use Refresh (non-standard) HTTP headers or the meta
equivalent, or Javascript, if they were implemented with HTML; in my view
scripting is an even worse option than Refresh.  The web has a pull,
user controlled, model of operation, but chat is designed for a push
mode of operation, which really needs the use of proper chat protocols.

Refresh was basically invented to simulate push (and actually marketed as
"server push" technology) to shift the balance away from the user to the
author, whilst not changing web servers, or requiring firewall policies
to be relaxed.  As well as philosophical considerations, by polling the
server, it puts an unnecessary load on the network.

You should use an appropriate technology, remembering that the original
aim of the web was to help locate resources of multiple forms, not to
do everything using HTTP and HTML.

(I've not freqented web chat servers, but I'm pretty sure that the only
reasons that forums were created were:

- NNTP doesn't provide a means of adding advertising;

- USENET makes it difficult (for good reasons) for ad hoc group creation.)
Received on Sunday, 4 February 2001 05:45:47 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 19 July 2011 18:13:53 GMT