- From: Ashok Malhotra <ashok.malhotra@oracle.com>
- Date: Sun, 03 Nov 2013 19:58:01 -0500
- To: "public-ldp-wg@w3.org" <public-ldp-wg@w3.org>
Received on Monday, 4 November 2013 00:58:32 UTC
Erik and I have been having an email exchange related to paging and, essentially, page stability. In the database world this is called cursor stability, See: rhttp://my.safaribooksonline.com/book/databases/db2/0738491195/identifying-isolation-level-differences/237 <http://my.safaribooksonline.com/book/databases/db2/0738491195/identifying-isolation-level-differences/237> for example. But I want to touch on a broader issue. With LDP we allow multiple users access to a web resource, and some of these users may be able to update the resource or some part of it. This takes us into database territory but we have steadfastly chosen to ignore functionality like - access control - transactions - locking We need to consider these because it will come back and bite us in the butt when, for example, users' updates are partially reflected (transactions). -- All the best, Ashok
Received on Monday, 4 November 2013 00:58:32 UTC