My suggestion is to write a unit test in Chromium's webkit_unit_test framework.
Adam
On Wed, Sep 19, 2012 at 1:50 PM, Alec Flett wrote:
> So this thread kinda died. Anyone have any suggestions? Where is JSC's
> SerializedScriptValue consistency tested?
>
> Alec
>
>
> On Tue, Sep 18, 2012 at 1:2
It isn't, it's never been a concern as our serialisation format is simple
enough to be hard to break. That said tests would be fine, i'm just not sure
how you would do them nicely.
--Oliver
On Sep 19, 2012, at 1:50 PM, Alec Flett wrote:
> So this thread kinda died. Anyone have any suggestion
So this thread kinda died. Anyone have any suggestions? Where is JSC's
SerializedScriptValue consistency tested?
Alec
On Tue, Sep 18, 2012 at 1:22 PM, Alec Flett wrote:
> Sorry I totally left out the "I expose this through Internals" - and adam
> has explained the rationale
>
> On Tue, Sep 18,
Sorry I totally left out the "I expose this through Internals" - and adam
has explained the rationale
On Tue, Sep 18, 2012 at 12:46 PM, Oliver Hunt wrote:
> What exactly are you trying to test here? The internal serialisation
> format isn't exposed anywhere (nor should it be).
>
> By definition
Where do you test that property?
Adam
On Tue, Sep 18, 2012 at 12:43 PM, Oliver Hunt wrote:
> JSC's SerializedScriptValue has always been versioned (having learned the
> horror of no versioning with localStorage :( )
>
> Newer formats (obviously) can't be read by older clients, but the
> seria
What exactly are you trying to test here? The internal serialisation format
isn't exposed anywhere (nor should it be).
By definition newer formats won't be backwards compatible, or are you trying to
ensure that newer deserialisers will be able to continue to deserialise old
content?
--Oliver
JSC's SerializedScriptValue has always been versioned (having learned the
horror of no versioning with localStorage :( )
Newer formats (obviously) can't be read by older clients, but the serialisation
is intentionally forwards compatible.
--Oliver
On Sep 18, 2012, at 12:36 PM, Adam Barth wrot
This is an interesting case because it's important for the
serialization format to be consistent across time (so that an
IndexedDB created at one point in time can work at another point in
time), but it's not important to be consistent across embedders
(because IndexedDB created by Safari don't nee
Background: some of the storage systems use SerializedScriptValue to
persist structured-clonable objects (
http://www.w3.org/TR/html5/common-dom-interfaces.html#safe-passing-of-structured-data)
- most of this is implemented in a V8 or JSC-specific implementation of
SerializedScriptValue.
I'm addin
9 matches
Mail list logo
