ISSUE-105

What information should be communicated about client state?

State:

CLOSED

Product:

wsc-xit

Raised by:

Thomas Roessler

Opened on:

2007-08-19

Description:

Whether or not the client keeps state that can be played back to the Web site is probably relevant security context information. Talking about cookie state display might be useful.

However, it is by now well-known that there are a number of mechanisms for keeping such state, including Flash, Google Gears, and Javascript/caching tricks.

Plugins and extensions can probably be dealt with by sufficiently generic language that covers them. What to do about clever caching of javascript code? Nothing at all?

Related Actions Items:

No related actions

Related emails:

1. Agenda: WSC WG distributed meeting, Wednesday, 2007-11-14 (from Mary_Ellen_Zurko@notesdev.ibm.com on 2007-11-13)
2. Meeting record: WSC WG f2f 2007-10-03 (from tlr@w3.org on 2007-10-25)
3. Editor's draft update: Some actions done, more to follow (from tlr@w3.org on 2007-10-10)
4. Draft Minutes: WSC WG face-to-face 2007-10-03 (from tlr@w3.org on 2007-10-10)
5. Re: Draft Minutes: WSC WG face-to-face 2007-10-03 (from ifette@google.com on 2007-10-09)
6. WSC Open Action Items (from Mary_Ellen_Zurko@notesdev.ibm.com on 2007-10-05)
7. Re: ISSUE-105: What information should be communicated about client state? [Techniques] (from johnath@mozilla.com on 2007-08-20)
8. ISSUE-105: What information should be communicated about client state? [Techniques] (from sysbot+tracker@w3.org on 2007-08-19)

Related notes:

Display change log