Re: Files on IndexedDB

Sorry to answer so late, busy with exams.

>> Then Chrome is taking REALLY liberally the interpretation, because on
>> some tests I removed the file and instead of raising an error it just
>> gave me an empty content and null modifiedTime and lenght...
>
>
> That sounds more like a simple bug/incomplete implementation than a liberal
> interpretation.  If lastModifiedDate or length are null, that's definitely a
> bug (neither one is nullable).
>
It's what they are currently doing. I prefer to think it's just an
incomplete implementation.


>> Yep :-) So, what other solution would be feasable? Both behaviours
>> (inmutable and live files) seems to be valid for some use cases...
>
>
> File objects aren't appropriate for live file updates, as Sicking said
> elsewhere.  (If I had a nicer solution I'd have proposed it already...)
>
So, besides Chrome hacks and being fully specification compliant,
there's no currently any way to detect when a file has changed nor
being deleted, isn't it?


--
"Si quieres viajar alrededor del mundo y ser invitado a hablar en un
monton de sitios diferentes, simplemente escribe un sistema operativo
Unix."
– Linus Tordvals, creador del sistema operativo Linux

Received on Wednesday, 12 June 2013 09:46:20 UTC