- From: <bugzilla@jessica.w3.org>
- Date: Mon, 07 Mar 2011 21:28:33 +0000
- To: public-script-coord@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=12248 --- Comment #8 from Cameron McCormack <cam@mcc.id.au> 2011-03-07 21:28:32 UTC --- (In reply to comment #7) > Storing into IndexDB is clearing such a boundary. But I don't think it would > be reasonable to say that every call from a script into a web API crosses such > a boundary. That would seem to require that essentially all interface > specification have to give some consideration to these issues. They > individually need to either be identified as a serialization boundary that > explicitly ensures that the serialization takes place or they will have to > explicitly deal with the possibility of accessor side-effects. You simply > can't pretend that these issues don't exist. What use cases do we have for that boundary not existing? Is it unreasonable for all instances where UAs inspect JS objects passed to them to be able to handle exceptions, side effects and resource exhaustion? If we can get away with always serializing so that we can deal with access side-effects up front, and not have to ignore accessor properties, I'd like to do that. -- Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
Received on Monday, 7 March 2011 21:28:34 UTC