All of this assumes that changing the state of a checkbox is something that
can be done even if the page has been updated on the server (i.e. the
message to update a checkbox identifies the checkbox to be updated and that change is applied to the copy of the page on the server; the entire page
need not be sent in every message).

Does this sound useful, or dangerous? Is there anything out there already
like this?

If you're worried about page corruption, you could do what VotePlugin does and store it in a local attachment in whatever format you fancy.

In 3.0, pages will have persistent metadata, so that should help *a lot* in these things.

/Janne

Reply via email to