Add LSID to Cache Manager
#1 Updated by Matt Jones over 13 years ago
This is mostly accomplished. The object manager uses LSIDs to identifiy cache
items. Some refactoring is being considered to make the old cache manager aware
of LSIDs. Also need to resolve the issue of using 'localhost' as an LSID
authority because it allows the possibility of conflicting LSIDs.
#2 Updated by Chad Berkley over 13 years ago
the objectcache will replace the datacachemanager as the main caching system in
kepler. the objectcache relies completely on LSIDs for unique identification of
objects. The infrastructure for dealing with lsids within kepler is complete.
There is an LSIDGenerator to create local lsids, an LSIDTree to keep track of
uniqueness and the KeplerLSID class itself that wraps the IBM LSID class so that
we can use local lsids.
there is a need for locally assigned lsids. the problem with using localhost as
the authority is that 2 people on 2 different computers could create the same
lsid. if we use another authority, a centralized ID store would need to be
implemented to garauntee uniqueness. Another idea that's been thrown around is
using some sort of encryption key as the object identifier. Currently, kepler
uses localhost as the authority. There needs to be more discussion on exactly
how this should be changed.