Re: [whatwg] postMessage and serialization

2008-03-01 Thread Jonas Sicking
Aaron Boodman wrote: Passing booleans, numbers and strings is trivial using the current API. Passing arrays of booleans and numbers is trivial too. Passing objects, or arrays of strings, arrays, or objects, is more complex, but as you point out, it can be done using JSON libraries. Since

Re: [whatwg] postMessage and serialization

2008-02-14 Thread Aaron Boodman
On Tue, Feb 12, 2008 at 4:57 PM, Ian Hickson [EMAIL PROTECTED] wrote: This was originally how the DOM Storage API worked, but there was significant pushback on this, resulting in the current string-only approach. When I came to writing the postMessage API, I considered that feedback and

Re: [whatwg] postMessage and serialization

2008-02-12 Thread Ian Hickson
On Mon, 11 Feb 2008, Aaron Boodman wrote: Has the topic of automatic serialization and deserialization of objects passed across postMessage() come up already? It seems like boolean, number, string, arrays, and objects should be supported. I realize that you can just use a json library,

[whatwg] postMessage and serialization

2008-02-11 Thread Aaron Boodman
Has the topic of automatic serialization and deserialization of objects passed across postMessage() come up already? It seems like boolean, number, string, arrays, and objects should be supported. I realize that you can just use a json library, but I wonder why we should force every application