webApplicationState-60 (was RE: ISSUE-60 (webApplicationState-48): Web Application State Management)

Opps... shortname error (application state problem :-) client (me) well out of sync!)

I don't know where 59 went... but tracker dispensed the number 60.

The shortname for this issue is "webApplicationState-60".

Stuart
--

> -----Original Message-----
> From: www-tag-request@w3.org [mailto:www-tag-request@w3.org]
> On Behalf Of Technical Architecture Group Issue Tracker
> Sent: 14 December 2007 10:24
> To: www-tag@w3.org
> Subject: ISSUE-60 (webApplicationState-48): Web Application
> State Management
>
>
> ISSUE-60 (webApplicationState-48): Web Application State Management
>
> http://www.w3.org/2001/tag/group/track/issues/
>
> Raised by: T.V. Raman
> On product:
>
> The TAG has openned a new issues, webApplicationState-48,
> around which to organise discussion of application state
> management techniques, partitioning of application state
> between origin servers and web clients, particularly rich web clients.
>
> An earlier draft finding "State in Web application design"
> http://www.w3.org/2001/tag/doc/state.html is relevant to this issue.
>
> In addition, recent threads on www-tag and related blog
> entries have discussed the use of URI fragId and user agent
> history stacks as a mechanism for managing client side state
> and for passing parameters from servers to rich web clients.
>
> http://lists.w3.org/Archives/Public/www-tag/2007Jul/0148
> http://xml-applications.blogspot.com/2007/11/toward-url-equali
> ty-for-web-clients-and.html
>
> Regards
>
> Stuart Williams
> for W3C TAG
>
>
>
>
>

Received on Friday, 14 December 2007 10:37:47 UTC