<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;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman";
color:black;}
a:link, span.MsoHyperlink
{color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{color:blue;
text-decoration:underline;}
pre
{margin:0in;
margin-bottom:.0001pt;
font-size:10.0pt;
font-family:"Courier New";
color:black;}
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>
<!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body bgcolor=white lang=EN-US link=blue vlink=blue>
<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 also think that just because a texture
comes off of HTTP doesn’t mean security can’t be applied.<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'>I can see scenarios to duplicate textures
across multiple web servers to improve downloading performance.<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'>I kind of look forward to the day when I
can apply URLs as textures and manage all my textures like I to for a web site.<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'>Regards,<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'><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
color=black face="Times New Roman"><span style='font-size:12.0pt;color:windowtext'>
<hr size=2 width="100%" align=center tabindex=-1>
</span></font></div>
<p class=MsoNormal><b><font size=2 color=black face=Tahoma><span
style='font-size:10.0pt;font-family:Tahoma;color:windowtext;font-weight:bold'>From:</span></font></b><font
size=2 color=black face=Tahoma><span style='font-size:10.0pt;font-family:Tahoma;
color:windowtext'> Diva Canto [mailto:diva@metaverseink.com] <br>
<b><span style='font-weight:bold'>Sent:</span></b> Wednesday, March 18, 2009
2:01 PM<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]
Accessing textures via HTTP [bayes]</span></font><font color=black><span
style='color:windowtext'><o:p></o:p></span></font></p>
</div>
<p class=MsoNormal><font size=3 color=black face="Times New Roman"><span
style='font-size:12.0pt'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=3 color=black face="Times New Roman"><span
style='font-size:12.0pt'>On the server-side, this can be made configurable,
default to false. If server admins want to serve jpgs, let's let them.<br>
Since this work is being done within the Idealist viewer, a separate issue is
whether you want Idealist to assume the existence of jpgs on the server or not.
But that's a client-side decision.<br>
<br>
Dahlia Trimble wrote: <o:p></o:p></span></font></p>
<p class=MsoNormal><font size=3 color=black face="Times New Roman"><span
style='font-size:12.0pt'>I don't think it's a goal of OpenSim to serve
texture assets to web browsers, nor should it be. Such a move would open doors to
texture piracy and reduce any incentives for content creators to distribute
their content on any OpenSim based platform. Grid operators who would want to
serve their texture assets as jpeg files and make them available to web
browsers could write their own conversion programs to do so. <o:p></o:p></span></font></p>
<div>
<p class=MsoNormal><font size=3 color=black face="Times New Roman"><span
style='font-size:12.0pt'><o:p> </o:p></span></font></p>
</div>
<div>
<p class=MsoNormal style='margin-bottom:12.0pt'><font size=3 color=black
face="Times New Roman"><span style='font-size:12.0pt'>Personally I would not
upload any of my textures to any service that distributes them as jpeg over
http unless they were creative commons textures.<o:p></o:p></span></font></p>
</div>
<div>
<p class=MsoNormal><font size=3 color=black face="Times New Roman"><span
style='font-size:12.0pt'><o:p> </o:p></span></font></p>
<div>
<p class=MsoNormal><font size=3 color=black face="Times New Roman"><span
style='font-size:12.0pt'>On Wed, Mar 18, 2009 at 9:51 AM, Tommi Laukkanen <<a
href="mailto:tommi.s.e.laukkanen@gmail.com" moz-do-not-send=true>tommi.s.e.laukkanen@gmail.com</a>>
wrote:<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=3 color=black face="Times New Roman"><span
style='font-size:12.0pt'>I think j2k is not really supported by any main stream
web browser<br>
software nor SDK APIs of different languages. Requiring opejpeg native<br>
lib to be included in all clients is not a good design decission. It<br>
would be much cleaner if you can operate with the nativate image<br>
manipulation API like System.Drawing in .NET. The converted JPEG's can<br>
be easily cached for now. It is only the SL viewers which require it<br>
because of some odd design decission from Linden Lab. I would not be<br>
surprised if in the future textures will be stored as png and<br>
converted to j2k for sl protocol. In high quality virtual world<br>
lossless texture format could be preferable. Odd codecs should not be<br>
forced on other protocols and clients based on ll behaviour.<br>
Especially if we are experimenting with new brand of client / protocol<br>
stacks like IdealistViewer and MXP.<br>
<br>
I truly hope metaverse is not stuck with openjepg and j2k. Those<br>
native libs tend to be more trouble than they are worth unless you<br>
absoletuly need them.<br>
<br>
Using the accept headers sounds like a good idea to me and if it is ok<br>
with the team I could implement region asset service as Diva suggested<br>
in the patch notes and Accept header support. I can put in cache as<br>
well to avoid performance bottleneck. About image quality: we will end<br>
up transforming from j2k anyway to some image format the client<br>
rendering engine supports. I can also convert from j2k to png instead<br>
of jpg to avoid any degradation as png is lossless format.<br>
<br>
One could also consider naming the class as proxy as it will proxy the<br>
call to local or remote asset server. Doing local caching on proxy is<br>
a pattern used in http proxies and it could work for us as well.<br>
Caching assets on region would lower the load on the grid asset<br>
database.<br>
</span></font><font color="#888888"><span style='color:#888888'><br>
-Tommi</span></font><o:p></o:p></p>
<div>
<div>
<p class=MsoNormal><font size=3 color=black face="Times New Roman"><span
style='font-size:12.0pt'>_______________________________________________<br>
Opensim-dev mailing list<br>
<a href="mailto:Opensim-dev@lists.berlios.de" moz-do-not-send=true>Opensim-dev@lists.berlios.de</a><br>
<a href="https://lists.berlios.de/mailman/listinfo/opensim-dev" target="_blank"
moz-do-not-send=true>https://lists.berlios.de/mailman/listinfo/opensim-dev</a><o:p></o:p></span></font></p>
</div>
</div>
</div>
<p class=MsoNormal><font size=3 color=black face="Times New Roman"><span
style='font-size:12.0pt'><o:p> </o:p></span></font></p>
</div>
<pre wrap=""><font size=2 color=black face="Courier New"><span
style='font-size:10.0pt'><o:p> </o:p></span></font></pre><pre
style='text-align:center'><font size=2 color=black face="Courier New"><span
style='font-size:10.0pt'>
<hr size=4 width="90%" align=center>
</span></font></pre><pre><font size=2 color=black face="Courier New"><span
style='font-size:10.0pt'><o:p> </o:p></span></font></pre><pre><font
size=2 color=black face="Courier New"><span style='font-size:10.0pt'>_______________________________________________<o:p></o:p></span></font></pre><pre><font
size=2 color=black face="Courier New"><span style='font-size:10.0pt'>Opensim-dev mailing list<o:p></o:p></span></font></pre><pre><font
size=2 color=black face="Courier New"><span style='font-size:10.0pt'><a
href="mailto:Opensim-dev@lists.berlios.de">Opensim-dev@lists.berlios.de</a><o:p></o:p></span></font></pre><pre><font
size=2 color=black face="Courier New"><span style='font-size:10.0pt'><a
href="https://lists.berlios.de/mailman/listinfo/opensim-dev">https://lists.berlios.de/mailman/listinfo/opensim-dev</a><o:p></o:p></span></font></pre><pre><font
size=2 color=black face="Courier New"><span style='font-size:10.0pt'> <o:p></o:p></span></font></pre>
<p class=MsoNormal><font size=3 color=black face="Times New Roman"><span
style='font-size:12.0pt'><o:p> </o:p></span></font></p>
</div>
</body>
</html>