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

RE: More scripting thoughts Pt. 2 (was RE: Accessible road maps)

From: Steven Dale <sdale@stevendale.com>
Date: Wed, 2 Jun 2004 17:40:11 -0400 (EDT)
Message-ID: <3373.>
To: <mikba@microsoft.com>
Cc: <sdale@stevendale.com>, <jim@e-media.co.uk>, <foliot@wats.ca>, <accessys@smart.net>, <Kurt_Mattes@bankone.com>, <w3c-wai-ig@w3.org>

Well, sort of.  I am thinking more of independant processing on the client
side.  For example, Instant Messaging runs on the client system and sends
information to another client system.  The Instant Messaging software does
processing on the clients system.  Whereas, displaying a form on a browser
window and sending the data to the server is not *really* doing any
processing of the data.  The form is there for collection, what processing
that is being done is done solely to send the data, maybe correct data if
verified on client, to the server.


Mike Barta said:
> It sounds like you are drawing a distinction of statefullness as the
> criterion of a 'program'.  Yes?
> -----Original Message-----
> From: w3c-wai-ig-request@w3.org [mailto:w3c-wai-ig-request@w3.org] On
> Behalf Of Steven Dale
> ...
> Ok what exactly is a webapp?  What program would you write using
> javascript+html?  All I hear from this list is that we need it to do
> javascript+fancy
> rollovers and dynamic menuing,  Partial page updates, form validation.
> Are these webapps?  I dont think so.
> Ok to firm up my point.  Have you used Instant Messaging?  That's a
> networked program, not a web app.  Sure there are some web interfaces to
> IM but they are interfaces not programs either.
> -Steve
Received on Wednesday, 2 June 2004 17:40:40 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 13 October 2015 16:21:28 UTC