[Opensim-dev] Proposal to subdivide the assets table

[Melanie]

The cache I'm writing will be generic. But one could put a thin 
type-safe wrapper around it, although C# style guides say to use 
generics directly.

Melanie


Stefan Andersson wrote:
> May I suggest that if we're going to look over the asset architecture, that we simplify the design, and at the same time open up for more flexible scenarios, by making each step implement a common asset transfer interface?
>  
> So, the local in-mem cache implements the same interface as the local db storage, which implements the same interface as the global asset server proxy which implements the same interface as the global asset server? (which, incidentally, itself could have an in-mem cache and obviously its db storage, which could be the same as the local caches)
> If we do so, plugging, re-using and re-routing asset flows by scenario will be childs play.
> Best regards,Stefan AnderssonTribal Media AB Join the 3d web revolution : http://tribalnet.se/ 
> 
> 
> 
>> Date: Fri, 27 Jun 2008 07:51:52 -0400> From: sean at dague.net> To: opensim-dev at lists.berlios.de> Subject: Re: [Opensim-dev] Proposal to subdivide the assets table> > On Fri, Jun 27, 2008 at 12:47:13PM +0100, Justin Clark-Casey wrote:> > Melanie wrote:> > > > > But assets are immutable and a region is a finite space. This makes > > > it an ideal situation for a persistent cache. While we cannot > > > totally remove centralized asset storage, almost all the above > > > points can be achieved by locally caching a region's used assets on > > > disk. This cache can be two-tiered:> > > > > > Tier 1: referenced assets, indefinite retention> > > Tier 2: unreferenced assets, short term retention> > > > > > This means, that textures on a prim would be cached locally forever, > > > but textures that make up the clothing of an avatar passing through > > > would be purged after a day or so.> > > For sounds, playing them would re-trigger the retention period, so > > > that looped sounds w
ill effectively be retained forever as well. > > > Same goes for any frequently used asset, however, we should probably > > > not cache object assets.> > > > +1 I think we need a persistent asset region cache. Moreover, this > > could be done today without any other redesign.> > +1 as well, for the same reasons as Justin. We can solve the issue> today through having a reasonable persistant cache mechanism, and not> add all kinds of other partitioning, bi-directional flow complexity> here.> > -Sean> > -- > __________________________________________________________________> > Sean Dague Mid-Hudson Valley> sean at dague dot net Linux Users Group> http://dague.net http://mhvlug.org> > There is no silver bullet. Plus, werewolves make better neighbors> than zombies, and they tend to keep the vampire population down.> __________________________________________________________________
> 
> 
> ------------------------------------------------------------------------
> 
> _______________________________________________
> Opensim-dev mailing list
> Opensim-dev at lists.berlios.de
> https://lists.berlios.de/mailman/listinfo/opensim-dev