<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:st1="urn:schemas-microsoft-com:office:smarttags" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=us-ascii">
<meta name=Generator content="Microsoft Word 11 (filtered medium)">
<!--[if !mso]>
<style>
v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style>
<![endif]--><o:SmartTagType
namespaceuri="urn:schemas-microsoft-com:office:smarttags" name="PersonName"/>
<!--[if !mso]>
<style>
st1\:*{behavior:url(#default#ieooui) }
</style>
<![endif]-->
<style>
<!--
/* Font Definitions */
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
{font-family:Verdana;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman";}
a:link, span.MsoHyperlink
{color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{color:purple;
text-decoration:underline;}
p
{mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman";}
span.EmailStyle18
{mso-style-type:personal-reply;
font-family:Arial;
color:navy;}
@page Section1
{size:8.5in 11.0in;
margin:1.0in 1.25in 1.0in 1.25in;}
div.Section1
{page:Section1;}
-->
</style>
</head>
<body lang=EN-US link=blue vlink=purple>
<div class=Section1>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'>I have started working on the Xenki viewer
which is a web base viewer and I can see wanting to support this. Right now
Xenki is based on XAML and XBAP. I have been playing with Silverlight based
web client as well but that is a bigger effort but where I like to get long
term. But both of these I can see getting images using a URL so I can use the
browser’s image caching and simply texture management. I suspect we can
create URLs based on <a href="http://www.assetserver.com/AvatarUUID/AssetUUID">http://www.assetserver.com/AvatarUUID/AssetUUID</a>
or some kind of CAPS concept, so the server can see if this avatar is logged in
and has permissions to retrieve that image. But I can also see if we can move
away from UUID to file names then that opens up to using every image in the
internet not just images that are uploaded into the grid.<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'>If we have something working let me know I
would be happy to play with it.<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'>Kevin Tweedy<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'>IRC: Mystical<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'><o:p> </o:p></span></font></p>
<div>
<div class=MsoNormal align=center style='text-align:center'><font size=3
face="Times New Roman"><span style='font-size:12.0pt'>
<hr size=2 width="100%" align=center tabindex=-1>
</span></font></div>
<p class=MsoNormal><b><font size=2 face=Tahoma><span style='font-size:10.0pt;
font-family:Tahoma;font-weight:bold'>From:</span></font></b><font size=2
face=Tahoma><span style='font-size:10.0pt;font-family:Tahoma'>
opensim-dev-bounces@lists.berlios.de
[mailto:opensim-dev-bounces@lists.berlios.de] <b><span style='font-weight:bold'>On
Behalf Of </span></b>Stefan Andersson<br>
<b><span style='font-weight:bold'>Sent:</span></b> Friday, May 01, 2009 8:36 AM<br>
<b><span style='font-weight:bold'>To:</span></b> <st1:PersonName w:st="on">opensim-dev@lists.berlios.de</st1:PersonName><br>
<b><span style='font-weight:bold'>Subject:</span></b> Re: [Opensim-dev]
Alternatively Identifying Assets using URL's</span></font><o:p></o:p></p>
</div>
<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=2 face=Verdana><span style='font-size:10.0pt;
font-family:Verdana'>It is my impression that adressing by uri/url has been a
goal for the last 1.5 years or so.<br>
<br>
I'd be interested in hearing if there's actually anybody _not_ wanting us to
work towards that.<br>
<br>
The only issue that I can see would be in regards to SL compatibility.
I have started to poc an approach where guid-based adressing of
resources is considered a thing purely between the viewer and the content
endpoint (aka the region) - that the region acts as a 'proxy' translating guids
to uris and back as needed. So far the code is merely stubs, so I haven't got
to the point of proofing it, but I believe you all understand what I'm saying.
Have a look at what uses the fairly new ContainsReferences method on
AssetBase to see where I was going.<br>
<br>
Best regards,<br>
Stefan Andersson<br>
<br>
<br>
<br>
<br>
> Date: Fri, 1 May 2009 08:56:57 +0300<br>
> From: tommi.s.e.laukkanen@gmail.com<br>
> To: <st1:PersonName w:st="on">opensim-dev@lists.berlios.de</st1:PersonName><br>
> Subject: [Opensim-dev] Alternatively Identifying Assets using URL's<br>
> <br>
> If we do not consider SL restrictions for a second and look to the<br>
> future it would be nice to discuss the following which popped out from<br>
> dahlias idea of supporting loading textures from websites directly and<br>
> Stefans suggestion of using strings as ids in the standard format<br>
> thread:<br>
> <br>
> It is good to consider supporting identification of assets by<br>
> traditional urls. Some public asset servers could be www servers or<br>
> svn http servers. As all 3d modeling programs are refering to<br>
> aggregate assets using file paths, it would be easy to upload the<br>
> model to SVN http server and then using viewer pull out the model and<br>
> aggregate assets for viewing. This could be alternative asset<br>
> distribution model. it could work through region asset cache or<br>
> directly from viewer to the http server. This could be much more<br>
> scalable than the current model. I realize this is a threat to the<br>
> data consistency as models and aggregate assets are not saved to<br>
> relational database which could safeguard relations. It is also viable<br>
> only for completely public content but I assume considerable portion<br>
> of the vw content is likely to be freely distributable.<br>
> <br>
> This would be in practice support for "importing" content from
web on the fly.<br>
> <br>
> -tommi<br>
> _______________________________________________<br>
> Opensim-dev mailing list<br>
> Opensim-dev@lists.berlios.de<br>
> https://lists.berlios.de/mailman/listinfo/opensim-dev<o:p></o:p></span></font></p>
</div>
</body>
</html>