to javadb to not to be, swing client caching is the question
 

I am toying with the idea of using a client side database (perhaps
javadb, perhaps berkley, perhaps a seperate caching solution) to store
client 'state'.

I think, if you have a very rich business client app with many, many
windows, forms, drop down lists, etc that there is undoubtably value
in caching a lot of reference locally. But not to the point that you
use up all of the clients memory doing so of course. To that end
perhaps a database is ideal to have a predefined memory allocation,
and use it in the most optimal fashion.

Since at that point I have all objects, I suppose it makes sense to
not remap to a relational database, rather use an object database
(perhaps as binary objects, perhaps as XML).

Anyone done this extensively with success?

thanks

Tim