<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=UTF-8" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Then, may I guess, some available options are:<br>
* "safe" platform-specific native libraries that provide handles
(hHandle style) to a packet subsystem<br>
or<br>
* re-write the transport to a portable implementation that
performs/scales under CIL<br>
<br>
First option requires management of platform portability, which APR can
help and probably reaches all platforms that CIL runs on. Exceptions
are a pain, however.<br>
<br>
Second option would be easy on the server side, but even if implemented
in CIL the support of it would require implementation in the viewers to
switch between either transport.<br>
<br>
I'm sure I'm not the first to suggest these on this list.<br>
<br>
Frisby, Adam wrote:
<blockquote
cite="midC2F948DA2AC0BF448A49E5F3148BF12AA03F7BE0@winxbeus02.exchange.xchg"
type="cite">
<meta http-equiv="Content-Type" content="text/html; ">
<meta name="Generator" content="Microsoft Word 12 (filtered medium)">
<style>
<!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
{font-family:Consolas;
panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";
color:black;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
pre
{mso-style-priority:99;
mso-style-link:"HTML Preformatted Char";
margin:0cm;
margin-bottom:.0001pt;
font-size:10.0pt;
font-family:"Courier New";
color:black;}
span.HTMLPreformattedChar
{mso-style-name:"HTML Preformatted Char";
mso-style-priority:99;
mso-style-link:"HTML Preformatted";
font-family:Consolas;
color:black;}
span.EmailStyle19
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page Section1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
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]-->
<div class="Section1">
<p class="MsoNormal"><span
style="font-size: 11pt; font-family: "Calibri","sans-serif"; color: rgb(31, 73, 125);">Using
unsafe blocks though is generally considered a bad idea(tm),
and has a good chance of breaking compatibility with things though.<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size: 11pt; font-family: "Calibri","sans-serif"; color: rgb(31, 73, 125);"><o:p> </o:p></span></p>
<p class="MsoNormal"><span
style="font-size: 11pt; font-family: "Calibri","sans-serif"; color: rgb(31, 73, 125);">Regards,<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size: 11pt; font-family: "Calibri","sans-serif"; color: rgb(31, 73, 125);"><o:p> </o:p></span></p>
<p class="MsoNormal"><span
style="font-size: 11pt; font-family: "Calibri","sans-serif"; color: rgb(31, 73, 125);">Adam<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size: 11pt; font-family: "Calibri","sans-serif"; color: rgb(31, 73, 125);"><o:p> </o:p></span></p>
<div
style="border-style: none none none solid; border-color: -moz-use-text-color -moz-use-text-color -moz-use-text-color blue; border-width: medium medium medium 1.5pt; padding: 0cm 0cm 0cm 4pt;">
<div>
<div
style="border-style: solid none none; border-color: rgb(181, 196, 223) -moz-use-text-color -moz-use-text-color; border-width: 1pt medium medium; padding: 3pt 0cm 0cm;">
<p class="MsoNormal"><b><span
style="font-size: 10pt; font-family: "Tahoma","sans-serif"; color: windowtext;"
lang="EN-US">From:</span></b><span
style="font-size: 10pt; font-family: "Tahoma","sans-serif"; color: windowtext;"
lang="EN-US">
<a class="moz-txt-link-abbreviated" href="mailto:opensim-dev-bounces@lists.berlios.de">opensim-dev-bounces@lists.berlios.de</a>
[<a class="moz-txt-link-freetext" href="mailto:opensim-dev-bounces@lists.berlios.de">mailto:opensim-dev-bounces@lists.berlios.de</a>] <b>On Behalf Of </b>Dzonatas<br>
<b>Sent:</b> Sunday, 17 August 2008 7:36 PM<br>
<b>To:</b> <a class="moz-txt-link-abbreviated" href="mailto:opensim-dev@lists.berlios.de">opensim-dev@lists.berlios.de</a><br>
<b>Subject:</b> Re: [Opensim-dev] Upcoming work on alternative client
stack<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">If unsafe blocks are allowed, then shuffle
optimizations
could be used. It would only be advantageous if the data is streamed.
The
packets are probably accumulated in a way that would cause more
overhead just
to sort them and stream them. If there are ones that can be arranged,
then it
may be practical.<br>
<br>
<br>
Melanie wrote: <o:p></o:p></p>
<pre>Not really. Two memory accesses to retrieve 2 values packed into one <o:p></o:p></pre>
<pre>byte are 2 accesses. in C#, C++, unsafe blocks or even assembly. <o:p></o:p></pre>
<pre>They remain inefficient.<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>Melanie<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre><o:p> </o:p></pre>
<pre>Kyle Hamilton wrote:<o:p></o:p></pre>
<pre> <o:p></o:p></pre>
<blockquote style="margin-top: 5pt; margin-bottom: 5pt;">
<pre>Could the unpackers be implemented more efficiently if they could run<o:p></o:p></pre>
<pre>in unsafe blocks?<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>-Kyle H<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>On Sun, Aug 17, 2008 at 6:33 PM, Melanie <a
href="mailto:melanie@t-data.com"><melanie@t-data.com></a> wrote:<o:p></o:p></pre>
<pre> <o:p></o:p></pre>
<blockquote style="margin-top: 5pt; margin-bottom: 5pt;">
<pre>Hi,<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>specific types, as we have now. What is it you don't like about what<o:p></o:p></pre>
<pre>we have now? With the framework we have to work with (C#) the<o:p></o:p></pre>
<pre>current implementation seems the best one we can get.<o:p></o:p></pre>
<pre>I have already shown in chat how unpackers lose efficiency with LL's<o:p></o:p></pre>
<pre>weird bitpacked data fields. This would show less performance, not<o:p></o:p></pre>
<pre>more. So I wonder what the point is?<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>Melanie<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre><o:p> </o:p></pre>
<pre>Mike Mazur wrote:<o:p></o:p></pre>
<pre> <o:p></o:p></pre>
<blockquote style="margin-top: 5pt; margin-bottom: 5pt;">
<pre>Hi,<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>On Mon, 18 Aug 2008 01:49:51 +0100<o:p></o:p></pre>
<pre>Melanie <a href="mailto:melanie@t-data.com"><melanie@t-data.com></a> wrote:<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre> <o:p></o:p></pre>
<blockquote style="margin-top: 5pt; margin-bottom: 5pt;">
<pre>if the packets are structs/arrays, be careful of boxing issues. You<o:p></o:p></pre>
<pre>would have no advantage from that if you have to eat the boxing<o:p></o:p></pre>
<pre>overhead instead.<o:p></o:p></pre>
<pre> <o:p></o:p></pre>
</blockquote>
<pre>Hm, that's a good point. I guess since Packet is a descendant of<o:p></o:p></pre>
<pre>object, no performance hit occurs.<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>What would be a good way to get around this?<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>Mike<o:p></o:p></pre>
<pre>_______________________________________________<o:p></o:p></pre>
<pre>Opensim-dev mailing list<o:p></o:p></pre>
<pre><a href="mailto:Opensim-dev@lists.berlios.de">Opensim-dev@lists.berlios.de</a><o:p></o:p></pre>
<pre><a
href="https://lists.berlios.de/mailman/listinfo/opensim-dev">https://lists.berlios.de/mailman/listinfo/opensim-dev</a><o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre><o:p> </o:p></pre>
<pre> <o:p></o:p></pre>
</blockquote>
<pre>_______________________________________________<o:p></o:p></pre>
<pre>Opensim-dev mailing list<o:p></o:p></pre>
<pre><a href="mailto:Opensim-dev@lists.berlios.de">Opensim-dev@lists.berlios.de</a><o:p></o:p></pre>
<pre><a
href="https://lists.berlios.de/mailman/listinfo/opensim-dev">https://lists.berlios.de/mailman/listinfo/opensim-dev</a><o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre> <o:p></o:p></pre>
</blockquote>
<pre>_______________________________________________<o:p></o:p></pre>
<pre>Opensim-dev mailing list<o:p></o:p></pre>
<pre><a href="mailto:Opensim-dev@lists.berlios.de">Opensim-dev@lists.berlios.de</a><o:p></o:p></pre>
<pre><a href="https://lists.berlios.de/mailman/listinfo/opensim-dev">https://lists.berlios.de/mailman/listinfo/opensim-dev</a><o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre><o:p> </o:p></pre>
<pre> <o:p></o:p></pre>
</blockquote>
<pre>_______________________________________________<o:p></o:p></pre>
<pre>Opensim-dev mailing list<o:p></o:p></pre>
<pre><a href="mailto:Opensim-dev@lists.berlios.de">Opensim-dev@lists.berlios.de</a><o:p></o:p></pre>
<pre><a href="https://lists.berlios.de/mailman/listinfo/opensim-dev">https://lists.berlios.de/mailman/listinfo/opensim-dev</a><o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre><o:p> </o:p></pre>
<pre> <o:p></o:p></pre>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</div>
<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>
<br>
</body>
</html>