GWT Local Database?

[Kyle Anderson]

I have a user application where a user loads a map with about
3000-5000 widgets on it. The user needs to be able to filter/sort/
modify these elements quickly. The server load is heavy, and GAE is
performing abominably.


My idea is to transfer all the elements to the client in a local
database such as the HTML5 local database. Have the user interact/
modify them directly in the client, send the database back to the
server, then update the dirty elements.


It's fine if my users are required to have HTML5, I'm not concerned
with this as its intended for a small set of users.

[Joseph Lust]

Be sure to check out the GWT-Mobile-WebKit database API.

Keep in mind that this could be a huge security hole for SQL injection. You'll need to ensure you escape everything coming back in that sqlLite DB. Then you'll also need a robust way to detect diffs.

It might be easier, if the user does not make that many changes, to just send back the differences and merge those.

Sincerely,

Joseph

[dominikz]

Just remember that there's a known issue with SQLite INSERT time. Google something like 'sqlite html5 insert time slow' and you'll see what I mean.

We bumped into that when writing our applications. They are on mobile browsers so it impacts us even more.