>An interesting aside, though, is that the current HTML5 draft includes local cursors. Can you believe it? What Boy Genius came up with THAT idea? (Yaaaaaaaaawn.) Sounds great in theory, but in practice there are a bunch of security and other concerns that haven't been addressed yet.

IMHO a local SqLite DB to cache remote DB queries in one or two "cursor" DB's (one as :memory:)
as well as locally installed lookup tables in a different DB
make more sense than keeping all of that in memory like ADO.Net.
If you want nHibernate object structure in your app, build from local DB,
but keep the border to SQL table "buffers" on the client machine -
and such a pattern can be enabled on PC, mobile devices and Browsers with HTML5.

As I was expecting something similar from posts in the last few months,
implementing such a component only looks better all the time -
could uncouple myself from some of the whims of bullshit-bingo driven development.

Added side benefits: possibility for less data on the wire
if implemented with cahcing strategies and partial persistence in mind
and less traffic if previous queries denormalized large sets heavyly to escape ADO.Net "datamunging"...

And yes, SQLite gets bonus points for being OS over anything MS can offer, offsetting some bad points.

my 0.001 EUR

thomas