#9 Client side object caching

[ted stockwell]

I beleive that it would be fairly straight-forward to add
transparent client-side object caching for
org.jlense.zone.j2ee zone connections.

Server-side OJB mapping will be configured to assigned
a unique ID to all objects. Also, all classes should be
configure to use proxies. Therefore any query submitted
to the server side will return proxies. Each proxies is
guaranteed to have a unique id. Therefore the 'real
object' may be looked up on the client side in a simple
hash map that saves objects indexed by id. Thus
saving a call to the server side to retrive the 'real' object
for any object that has already been sent once to the
client.

[Nobody/Anonymous]

Logged In: NO

You could consider adapting the jakarta jcs project for client
side caching??

[ted stockwell]

Logged In: YES
user_id=64586

Wow, JCS looks cool. I'm all about reuse and not reinventing
the wheel so I would definitely like to use JCS instead of
inventing my own caching scheme.
I am currently using Jakarta OJB for O/R mapping and will
need to do research on using JCS and using JCS with OJB
before proceeding. Have you used JCS before? Got any
good links?

BTW, I can't tell who posted this message because you
weren't logged in. Thanks for the tip though!