W3C home > Mailing lists > Public > public-webapps@w3.org > October to December 2009

WebSimpleDB object caching

From: Kris Zyp <kris@sitepen.com>
Date: Sat, 07 Nov 2009 21:12:40 -0700
Message-ID: <4AF64538.1090508@sitepen.com>
To: Web Applications Working Group WG <public-webapps@w3.org>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
 
Is there any intended restrictions on caching of objects returned by
queries and gets with WebSimpleDB? For example (using the address book
example in the spec):

|database = window.openDatabase('AddressBook', '1', 'Address Book', true);
database.transaction(function(Transaction txn) {
  var store = txn.getEntityStore('Contact');
  var allCursor = store.entities();
  var lCursor = store.getIndex('ContactName').entities('L');
  var l1 = lCursor.next();
  l1 = lCursor.next();
  var l2 = allCursor.next();

Now, is there any intended requirement that l1==l2 must be false even
if ||they represent the same record (that is l1["id"] === l2["id"]) or
can cursors potentially reuse JS objects? Also should store.get(l1.id)
== l1 be false as well? In other words, if one does l2.number =
'3322', is there any guarantee that l1.number would be unchanged (or
would be changed)?
Thanks,

- --
Kris Zyp
SitePen
(503) 806-1841
http://sitepen.com
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
 
iEYEARECAAYFAkr2RTgACgkQ9VpNnHc4zAwU4wCeIELYoOJX+WuUwpPhmp9Z4XHP
GWUAnjsju7ZfFQssRkrKAPyg5TJhMhNt
=Dws5
-----END PGP SIGNATURE-----
Received on Sunday, 8 November 2009 04:13:26 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 18:49:35 GMT