I don't think we should worry about underlying file changes.
If the app wants to cut a file into parts and copy them separately, then
perhaps the app should first copy the file into a private area. (I'm
presuming that one day, we'll have the concept of a chroot'd private file
storage area for a
On Thu, Jan 14, 2010 at 11:58 PM, Darin Fisher da...@chromium.org wrote:
I don't think we should worry about underlying file changes.
If the app wants to cut a file into parts and copy them separately, then
perhaps the app should first copy the file into a private area. (I'm
presuming that
Hi there,
I just found out that this group is very interesting and it stopped because
of several reasons in 2007.
We are in 2010 now and I think the momentum is there for declarative
application development.
We have a proposal and want to make it to an open specification.
The question: how to
I'm sorry for my mistake then. I would like to participate.
Nice to hear the the group is much alive and active.
Thanks for the note.
Regards,
Rokesh Jankie
---
QAFE
powered by experience quality
Website : http://www.qafe.com/
Youtube : http://youtube.com/qafechannel
LinkedIn:
Rokesh,
On Jan 15, 2010, at 6:43 AM, ext Rokesh Jankie wrote:
I just found out that this group is very interesting and it stopped
because of several reasons in 2007.
Perhaps you are thinking of the Web Applications Format (WAF) WG and
Web API WG which both ended in 2008 (and as Lachan
On Fri, Jan 15, 2010 at 10:19 AM, Dmitry Titov dim...@chromium.org wrote:
Nobody proposed locking the file. Sorry for being unclear if that sounds
like it. Basically it's all about timestamps.
As Chris proposed earlier, a read operation can grab the timestamp of the
file before and after
On Fri, Jan 15, 2010 at 10:19 AM, Dmitry Titov dim...@chromium.org wrote:
Nobody proposed locking the file. Sorry for being unclear if that sounds
like it. Basically it's all about timestamps.
As Chris proposed earlier, a read operation can grab the timestamp of the
file before and after
Hi,
I've been reading the new IndexedDB spec as published here:
http://www.w3.org/TR/IndexedDB/
My first impression is that this simpler than WebSimpleDB, but not too
simple. I'm happy to see detached readers being mentioned.
There's one other piece of the concurrency story that could be
On Fri, Jan 15, 2010 at 11:42 AM, Dmitry Titov dim...@chromium.org wrote:
On Fri, Jan 15, 2010 at 10:36 AM, Jonas Sicking jo...@sicking.cc wrote:
On Fri, Jan 15, 2010 at 10:19 AM, Dmitry Titov dim...@chromium.org
wrote:
Nobody proposed locking the file. Sorry for being unclear if that
