On Tue, Jul 3, 2012 at 4:08 PM, Greg Billock wrote:
> Do you think the way my patch does this, by exposing two new methods on
> the BlobController for notifying serialization and deserialization, will be
> sufficient?
For IndexedDB, it looks to me that notifications like this (or on the
> Blob
Do you think the way my patch does this, by exposing two new methods on the
BlobController for notifying serialization and deserialization, will be
sufficient?
For IndexedDB, it looks to me that notifications like this (or on the
BlobData ID, as you propose) will be critical -- the IndexedDB will
I think revamping our Blob handling is one of the projects that I should be
working on next. What we have now is proving to be too difficult to work
with in a variety of ways.
The more i look at this particular difficulty with sending blobs within
serialized values (within chromium), the more conv
On Tue, Jun 26, 2012 at 10:19 AM, Greg Billock wrote:
> I've been working with Michael Nordman on a problem related to Blob
> serialization. Currently, if we serialize a Blob, there's no
> notification to the BlobRegistry, so the serialized Blob will be
> garbage collected at an indeterminate tim
I've been working with Michael Nordman on a problem related to Blob
serialization. Currently, if we serialize a Blob, there's no
notification to the BlobRegistry, so the serialized Blob will be
garbage collected at an indeterminate time if the context in which it
was created is closed. This lifetim
5 matches
Mail list logo
