David Hopwood wrote:
> Douglas Crockford wrote:
>> --- In firstname.lastname@example.org, David Hopwood <david.hopwood@...> wrote:
>>> Douglas Crockford wrote, in May:
>>>> How does this fit in a capability network?
>>> # Communication is restricted only to JSON text. JSON text allows
>>> # exchange of simple or complex data structures without the capability
>>> Restricting to JSON is a good idea only if there exists a standardized
>>> to do that using 'eval'.
>> The parseJSON method is available at http://www.json.org/js.html
I see that even that page says:
# To convert a JSON text into an object, use the eval() function.
before pointing out why you shouldn't do that. It should be changed
to be less self-contradictory.
>> It will be standard equipment in the next edition of ECMAScript.
The .toJSONString() methods specified and implemented at
> will not terminate successfully when
passed a cyclic structure. I don't think it is OK to place a requirement
on the caller to pass an acyclic structure, without specifying what
happens if it is cyclic.
If for some reason it isn't considered desirable to pass cyclic
structures between compartments (vats, iframes, etc.), then this
should be specified to cause an exception, rather than a stack
overflow exception being a side-effect of a particular implementation.
Another problem with those methods is:
// Values without a JSON representation are ignored.
This is broken; values without a JSON representation should cause an
> That's good. I still think that exchanging deep-copied objects directly
> would be more convenient.
... and would correctly handle cycles.
> It also allows immutable objects to be shared
> between sender and recipient, rather than being copied unnecessarily (as
> well as saving the memory for the [Unicode] JSON string).
Actually this is not straightforward to implement because of the ability
compartment is to be allowed to change the prototypes for object, String,
etc., then objects can't safely be shared between compartments [*].
I consider this a language design flaw, BTW.
[*] At least, not without some deep magic, such as treating an object as
having different prototypes depending on what compartment it is being
used from. Actually, forget I mentioned that; I disclaim all
responsibility for that idea ;-)
> Note that if the deep copy is defined to be equivalent to converting to
> JSON and back using the JSON bindings of the sending and receiving
> languages, there is no cross-language interoperability problem with this.
David Hopwood <david.hopwood@...