If you write it, I'll use it. <s> I think it makes a lot of sense. Bring the first <n> rows back, and asynchronously continue getting the data after that, with rules for caching, etc. This would also give local cursors to query against, just like that product Microsoft had that was some kind of animal, wasn't it?

re: dumping Silverlight -- doing so publicly might allow them to buy Adobe, since they would not have a competitive product. I wonder if the meeting MS had with Adobe a couple of weeks ago was to see if they could do something before the Redmond PDC, but it didn't work out. They sure have come up empty, and left developers in the lurch. They are working hard to develop that reputation, as a company that leaves developers in the lurch. "Where are they going to go, anyway?" I can imagine MS management saying, having paid little attention to what is going on around them. Right now, if you are a Silverlight for the web developer, good luck getting that next enterprise (where they are about what you use as tools) contract. Meanwhile, the Java development house can pitch that IBM and Oracle are backing the Java stack, and it's not going to be going away. What a mess.

Hank

>>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