W3C home > Mailing lists > Public > w3c-wai-gl@w3.org > April to June 2001

Re: Updating 2.4, re-revised

From: Matt May <mcmay@bestkungfu.com>
Date: Thu, 31 May 2001 09:31:51 -0700
Message-ID: <002501c0e9ef$4268e4c0$6501a8c0@sttln1.wa.home.com>
To: "Adam Victor Reed" <areed2@calstatela.edu>, <w3c-wai-gl@w3.org>
----- Original Message -----
From: "Adam Victor Reed" <areed2@calstatela.edu>

> And it is not difficult to design bypass
> technologies that will still meet legitimate security and economic
> constraints.

I disagree. Timeouts such as those present in Dell's site (along with those
at my former companies) are based on hard business rules on the back end.
Expedia needs you to lock in your reservation so it can relay that request
to the computerized reservation system it gets its data from. (And it uses
meta refreshes to keep the HTTP connection alive while it contacts the slow
pathetic creature.) HomeGrocer and Webvan needed to accurately manage
delivery trucks and merchandise in the best possible manner. Resource
management is critical in e-commerce.

Ticketmaster is an extreme example: they require transactions to be
completed in 5 minutes, or they release reserved tickets back into the pool.
This isn't something they can change trivially, because they're using the
same reservation system in stores nationwide. And auctions all have timeouts
that can't be shifted.

It should be noted that the only sites where this presents an economic
barrier to the content provider are e-commerce sites, and it has been
suggested before that web content and web applications (such as those found
in e-com) have different rules. This is one rule that should definitely be
applied to static content, but cannot be applied to many web applications.

-
m
Received on Thursday, 31 May 2001 12:32:52 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 7 December 2009 10:47:10 GMT