<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-15"
http-equiv="Content-Type">
<title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
<br>
<br>
Stefan Andersson wrote:
<blockquote cite="mid:BLU134-W15529E3C3A9351BAA5A0F1D5B50@phx.gbl"
type="cite">
<style>
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 10pt;
font-family:Verdana
}
</style>Um. Having immutable assets do bring a number of optimization
shortcuts. I'm not saying it's all good - merely that it's not all bad.<br>
<br>
The OpenSim solution, as always, is to address each case by itself, and
to make divergence optional.<br>
<br>
So, maybe region map textures should be overwriteable. Maybe some
scripts should be overwriteable as well, maybe only on some type of
scripts. Maybe we should have a table enumerating what assetIds now
point to newer assetIds.<br>
</blockquote>
Yes, +1<br>
<blockquote cite="mid:BLU134-W15529E3C3A9351BAA5A0F1D5B50@phx.gbl"
type="cite"> <br>
Maybe the real problem is that we are talking about 'assets' and
'textures' instead of 'prim face textures', 'sculptie maps', 'photos',
'region map images', 'script sources', 'sounds', 'prims in inventory',
'notecards', 'animations' - my point being that we can probably
implement various configurable strategies for each of them, linden
viewer or no linden viewer.<br>
<br>
</blockquote>
Yes, +1000<br>
<blockquote cite="mid:BLU134-W15529E3C3A9351BAA5A0F1D5B50@phx.gbl"
type="cite">Best regards,<br>
Stefan Andersson<br>
Tribal Media AB<br>
<br>
> Date: Wed, 18 Feb 2009 16:37:12 +0100<br>
> From: <a class="moz-txt-link-abbreviated" href="mailto:dirk.krause@pixelpark.com">dirk.krause@pixelpark.com</a><br>
> To: <a class="moz-txt-link-abbreviated" href="mailto:opensim-dev@lists.berlios.de">opensim-dev@lists.berlios.de</a><br>
> Subject: Re: [Opensim-dev] oddities with asset storage<br>
> <br>
> ...<br>
> <br>
> >> This would mean that any grid runs into a severe problem
over time.<br>
> <br>
> >> Yep :). On a standalone one could implement some cleanup
scheme<br>
> which checks everything to see<br>
> >> if an asset is still referenced, and deletes that asset
if it is not.<br>
> >> In grid mode this is a much more difficult problem since
references<br>
> are scattered across many different<br>
> >> regions servers. The situation is even worse if you are
running a<br>
> grid where not all of them are<br>
> >> guaranteed to be connected.<br>
> <br>
> But isn't that ... horrible? (in lack of a better/worse word.)<br>
> <br>
> As I said yesterday, IMHO there is no real need to think about<br>
> optimizations when you have<br>
> a serious blocker like this. I would even go so far that this is a
major<br>
> roadblock for grid based technologies per se. (grid as in
Rosedale's<br>
> 'Happily now, Second Life has been proven to exist. If we
disappeared<br>
> tomorrow, the grid would be rebuilt by you.')<br>
> <br>
> I take it the bad news is that any proposed solution to this
breaks SL<br>
> compatibility?<br>
> <br>
> Maybe now would be a good time to take a step away from it.<br>
> <br>
> _______________________________________________<br>
> Opensim-dev mailing list<br>
> <a class="moz-txt-link-abbreviated" href="mailto:Opensim-dev@lists.berlios.de">Opensim-dev@lists.berlios.de</a><br>
> <a class="moz-txt-link-freetext" href="https://lists.berlios.de/mailman/listinfo/opensim-dev">https://lists.berlios.de/mailman/listinfo/opensim-dev</a><br>
<br>
<pre wrap="">
<hr size="4" width="90%">
_______________________________________________
Opensim-dev mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Opensim-dev@lists.berlios.de">Opensim-dev@lists.berlios.de</a>
<a class="moz-txt-link-freetext" href="https://lists.berlios.de/mailman/listinfo/opensim-dev">https://lists.berlios.de/mailman/listinfo/opensim-dev</a>
</pre>
</blockquote>
</body>
</html>