I agree! For the overhead of handling the well known problems of cacheable_data (e.g. locking during updates) this solves every objection that I can think of.
Most importantly this ensures that there is always a resolution for the identifier. A simple history file (journal?) can track changes made to archived identifiers (i.e. a list of changes made to the cache - analogous to a file system journal). As I think of it there are several ways to handle this problem, all of which fit nicely within the general concept that you have made. On Sun, Aug 29, 2010 at 10:06 AM, <[email protected]> wrote: > More generally, > > protocol://authority/resource_type/resource_id[/cacheable_data] > > The more I look at this, the more I like it. > >
_______________________________________________ Opensim-dev mailing list [email protected] https://lists.berlios.de/mailman/listinfo/opensim-dev
