Talk:Central Services - Revision history

https://wiki.secondlife.com/w/index.php?action=history&feed=atom&title=Talk%3ACentral_Services Talk:Central Services - Revision history 2026-06-05T13:09:01Z Revision history for this page on the wiki MediaWiki 1.42.1 https://wiki.secondlife.com/w/index.php?title=Talk:Central_Services&diff=34353&oldid=prev Burhop Piccard at 17:43, 4 October 2007 2007-10-04T17:43:28Z

<p></p> <table style="background-color: #fff; color: #202122;" data-mw="interface"> <col class="diff-marker" /> <col class="diff-content" /> <col class="diff-marker" /> <col class="diff-content" /> <tr class="diff-title" lang="en"> <td colspan="2" style="background-color: #fff; color: #202122; text-align: center;">← Older revision</td> <td colspan="2" style="background-color: #fff; color: #202122; text-align: center;">Revision as of 10:43, 4 October 2007</td> </tr><tr><td colspan="2" class="diff-lineno" id="mw-diff-left-l25">Line 25:</td> <td colspan="2" class="diff-lineno">Line 25:</td></tr> <tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br></td></tr> <tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>* PS. Small point: note that '''edges''' of target regions are only a special (but common) case of region adjacency. A portal in particular can provide access directly into the interior of a target region, and in most cases would do exactly that. --[[User:Morgaine Dinova|Morgaine Dinova]] 06:41, 25 September 2007 (PDT)</div></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>* PS. Small point: note that '''edges''' of target regions are only a special (but common) case of region adjacency. A portal in particular can provide access directly into the interior of a target region, and in most cases would do exactly that. --[[User:Morgaine Dinova|Morgaine Dinova]] 06:41, 25 September 2007 (PDT)</div></td></tr> <tr><td colspan="2" class="diff-side-deleted"></td><td class="diff-marker" data-marker="+"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div><ins style="font-weight: bold; text-decoration: none;"></ins></div></td></tr> <tr><td colspan="2" class="diff-side-deleted"></td><td class="diff-marker" data-marker="+"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div><ins style="font-weight: bold; text-decoration: none;">===Security===</ins></div></td></tr> <tr><td colspan="2" class="diff-side-deleted"></td><td class="diff-marker" data-marker="+"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div><ins style="font-weight: bold; text-decoration: none;"></ins></div></td></tr> <tr><td colspan="2" class="diff-side-deleted"></td><td class="diff-marker" data-marker="+"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div><ins style="font-weight: bold; text-decoration: none;">I'd like to understand the Central Services a bit better in the context or running inside an Intranet. Companies can not use Second Life to its full potential because of security concerns. There is certainly a business case for keeping a region and all its comunication traffic inside a Intranet that the comany can control. An avatar could go out into the rest of SL but only those inside the Intranet could access the region inside the Intranet. </ins></div></td></tr> <tr><td colspan="2" class="diff-side-deleted"></td><td class="diff-marker" data-marker="+"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div><ins style="font-weight: bold; text-decoration: none;"></ins></div></td></tr> <tr><td colspan="2" class="diff-side-deleted"></td><td class="diff-marker" data-marker="+"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div><ins style="font-weight: bold; text-decoration: none;">This seems doable except for maybe the Central Services (specifically Identity). How will the architecture be done so that companies feel secure? Will Central Services create a problem here?--[[User:Burhop Piccard|Burhop Piccard]] 10:43, 4 October 2007 (PDT)</ins></div></td></tr> </table>

Burhop Piccard https://wiki.secondlife.com/w/index.php?title=Talk:Central_Services&diff=32676&oldid=prev Morgaine Dinova at 14:12, 25 September 2007 2007-09-25T14:12:06Z

<p></p> <table style="background-color: #fff; color: #202122;" data-mw="interface"> <col class="diff-marker" /> <col class="diff-content" /> <col class="diff-marker" /> <col class="diff-content" /> <tr class="diff-title" lang="en"> <td colspan="2" style="background-color: #fff; color: #202122; text-align: center;">← Older revision</td> <td colspan="2" style="background-color: #fff; color: #202122; text-align: center;">Revision as of 07:12, 25 September 2007</td> </tr><tr><td colspan="2" class="diff-lineno" id="mw-diff-left-l24">Line 24:</td> <td colspan="2" class="diff-lineno">Line 24:</td></tr> <tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>: Certainly we don't want regions to be doing precision culling and clipping --- under the current static model, region servers don't scale, so this work '''must''' be done by the clients, which always scale linearly (or higher, with multicore). What's more, it's most definitely the client's choice which objects to process further for viewing, so region occupancy information supplied by the target region should never dictate that all the supplied occupants must be fully retrieved. Similar considerations apply for requests from the agent, in that only a few aspects of objects in the target region will be relevant, eg. boundary box information. --[[User:Morgaine Dinova|Morgaine Dinova]] 07:00, 25 September 2007 (PDT)</div></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>: Certainly we don't want regions to be doing precision culling and clipping --- under the current static model, region servers don't scale, so this work '''must''' be done by the clients, which always scale linearly (or higher, with multicore). What's more, it's most definitely the client's choice which objects to process further for viewing, so region occupancy information supplied by the target region should never dictate that all the supplied occupants must be fully retrieved. Similar considerations apply for requests from the agent, in that only a few aspects of objects in the target region will be relevant, eg. boundary box information. --[[User:Morgaine Dinova|Morgaine Dinova]] 07:00, 25 September 2007 (PDT)</div></td></tr> <tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br></td></tr> <tr><td class="diff-marker" data-marker="−"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #ffe49c; vertical-align: top; white-space: pre-wrap;"><div>* PS. Small point: note that '''edges''' of target regions are only a special (but common) case of region adjacency. A portal in particular can provide access directly into the interior of a target region, and in most <del style="font-weight: bold; text-decoration: none;">case </del>would do exactly that. --[[User:Morgaine Dinova|Morgaine Dinova]] 06:41, 25 September 2007 (PDT)</div></td><td class="diff-marker" data-marker="+"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div>* PS. Small point: note that '''edges''' of target regions are only a special (but common) case of region adjacency. A portal in particular can provide access directly into the interior of a target region, and in most <ins style="font-weight: bold; text-decoration: none;">cases </ins>would do exactly that. --[[User:Morgaine Dinova|Morgaine Dinova]] 06:41, 25 September 2007 (PDT)</div></td></tr> </table>

Morgaine Dinova https://wiki.secondlife.com/w/index.php?title=Talk:Central_Services&diff=32675&oldid=prev Morgaine Dinova: /* Zha's addon */ 2007-09-25T14:11:02Z

<p><span dir="auto"><span class="autocomment">Zha's addon</span></span></p> <table style="background-color: #fff; color: #202122;" data-mw="interface"> <col class="diff-marker" /> <col class="diff-content" /> <col class="diff-marker" /> <col class="diff-content" /> <tr class="diff-title" lang="en"> <td colspan="2" style="background-color: #fff; color: #202122; text-align: center;">← Older revision</td> <td colspan="2" style="background-color: #fff; color: #202122; text-align: center;">Revision as of 07:11, 25 September 2007</td> </tr><tr><td colspan="2" class="diff-lineno" id="mw-diff-left-l16">Line 16:</td> <td colspan="2" class="diff-lineno">Line 16:</td></tr> <tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br></td></tr> <tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>* Adding a bit more to "Tell me what an agent looking into your region from relative coordinate X.Y.Z needs to know":</div></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>* Adding a bit more to "Tell me what an agent looking into your region from relative coordinate X.Y.Z needs to know":</div></td></tr> <tr><td class="diff-marker" data-marker="−"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #ffe49c; vertical-align: top; white-space: pre-wrap;"><div>: Note that it's not functionally any different making these requests from inside or outside of that region --- both types of request need a source coordinate reference for spatial relevance sorting. As you say, only the relative coordinate w.r.to the target region's space really matters, not the absolute coordinate within the requesting region. <del style="font-weight: bold; text-decoration: none;">Indeed</del>, given that portal apertures can be moved around at will<del style="font-weight: bold; text-decoration: none;">, </del>and even animated, <del style="font-weight: bold; text-decoration: none;">it </del>would be <del style="font-weight: bold; text-decoration: none;">a mistake to require </del>the target region to <del style="font-weight: bold; text-decoration: none;">perform the required mapping on each request: </del> <del style="font-weight: bold; text-decoration: none;">let the requester suffer the overhead of being overly clever, so always compute the needed </del>''<del style="font-weight: bold; text-decoration: none;">relative</del>'' <del style="font-weight: bold; text-decoration: none;">coordinate on each request</del>.</div></td><td class="diff-marker" data-marker="+"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div>: Note that it's not functionally any different making these requests from inside or outside of that region --- both types of request need a source coordinate reference for spatial relevance sorting. As you say, only the relative coordinate w.r.to the target region's space really matters, not the absolute coordinate within the requesting region. <ins style="font-weight: bold; text-decoration: none;">However</ins>, given that portal apertures can be moved around at will and even animated <ins style="font-weight: bold; text-decoration: none;">(mirrors come to mind)</ins>, <ins style="font-weight: bold; text-decoration: none;">note that both a coordinate and a viewing vector </ins>would be <ins style="font-weight: bold; text-decoration: none;">required if </ins>the target region <ins style="font-weight: bold; text-decoration: none;">is </ins>to <ins style="font-weight: bold; text-decoration: none;">supply direction-sensitive data. </ins> <ins style="font-weight: bold; text-decoration: none;">(</ins>''<ins style="font-weight: bold; text-decoration: none;">But see below</ins>'' .<ins style="font-weight: bold; text-decoration: none;">.. delivering highly specific occupancy data may be inappropriate.)</ins></div></td></tr> <tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br></td></tr> <tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>: The information returned is not necessarily culled as a function of distance either: for example, a mountain on the far side of a region would become visible even when you approach the near side. It still needs to be presented to the agent for passing to the client as proxy and/or sent directly to the client. Despite the large topological distance to the mountain, a modern client will still display the remote entity, with CLOD and other techniques manipulating the rendering resolution appropriately.</div></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>: The information returned is not necessarily culled as a function of distance either: for example, a mountain on the far side of a region would become visible even when you approach the near side. It still needs to be presented to the agent for passing to the client as proxy and/or sent directly to the client. Despite the large topological distance to the mountain, a modern client will still display the remote entity, with CLOD and other techniques manipulating the rendering resolution appropriately.</div></td></tr> </table>

Morgaine Dinova https://wiki.secondlife.com/w/index.php?title=Talk:Central_Services&diff=32674&oldid=prev Morgaine Dinova at 14:00, 25 September 2007 2007-09-25T14:00:45Z

<p></p> <table style="background-color: #fff; color: #202122;" data-mw="interface"> <col class="diff-marker" /> <col class="diff-content" /> <col class="diff-marker" /> <col class="diff-content" /> <tr class="diff-title" lang="en"> <td colspan="2" style="background-color: #fff; color: #202122; text-align: center;">← Older revision</td> <td colspan="2" style="background-color: #fff; color: #202122; text-align: center;">Revision as of 07:00, 25 September 2007</td> </tr><tr><td colspan="2" class="diff-lineno" id="mw-diff-left-l20">Line 20:</td> <td colspan="2" class="diff-lineno">Line 20:</td></tr> <tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>: The information returned is not necessarily culled as a function of distance either: for example, a mountain on the far side of a region would become visible even when you approach the near side. It still needs to be presented to the agent for passing to the client as proxy and/or sent directly to the client. Despite the large topological distance to the mountain, a modern client will still display the remote entity, with CLOD and other techniques manipulating the rendering resolution appropriately.</div></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>: The information returned is not necessarily culled as a function of distance either: for example, a mountain on the far side of a region would become visible even when you approach the near side. It still needs to be presented to the agent for passing to the client as proxy and/or sent directly to the client. Despite the large topological distance to the mountain, a modern client will still display the remote entity, with CLOD and other techniques manipulating the rendering resolution appropriately.</div></td></tr> <tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br></td></tr> <tr><td class="diff-marker" data-marker="−"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #ffe49c; vertical-align: top; white-space: pre-wrap;"><div>: It's worth noting that the above approach may rapidly become obsolete, if it is not so already. The target region occupancy is not a large body of data in the context of today's machinery (only the per-object data really bloats it up), so it may be quite efficient for all occupancy data to be delivered in one fell swoop if the target region finds that best. In other words, the supplied relative coordinate is really only a heuristic hint to the target region. <del style="font-weight: bold; text-decoration: none;"> </del>Certainly we don't want regions to be doing precision culling and clipping --- under the current static model, region servers don't scale, so this work '''must''' be done by the clients, which always scale linearly (or higher, with multicore). --[[User:Morgaine Dinova|Morgaine Dinova]] <del style="font-weight: bold; text-decoration: none;">06</del>:<del style="font-weight: bold; text-decoration: none;">24</del>, 25 September 2007 (PDT)</div></td><td class="diff-marker" data-marker="+"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div>: It's worth noting that the above approach may rapidly become obsolete, if it is not so already. The target region occupancy is not a large body of data in the context of today's machinery (only the per-object data really bloats it up), so it may be quite efficient for all occupancy data to be delivered in one fell swoop if the target region finds that best. In other words, the supplied relative coordinate is really only a heuristic hint to the target region.</div></td></tr> <tr><td colspan="2" class="diff-side-deleted"></td><td class="diff-marker" data-marker="+"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div> </div></td></tr> <tr><td colspan="2" class="diff-side-deleted"></td><td class="diff-marker" data-marker="+"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div><ins style="font-weight: bold; text-decoration: none;">: </ins>Certainly we don't want regions to be doing precision culling and clipping --- under the current static model, region servers don't scale, so this work '''must''' be done by the clients, which always scale linearly (or higher, with multicore). <ins style="font-weight: bold; text-decoration: none;">What's more, it's most definitely the client's choice which objects to process further for viewing, so region occupancy information supplied by the target region should never dictate that all the supplied occupants must be fully retrieved. Similar considerations apply for requests from the agent, in that only a few aspects of objects in the target region will be relevant, eg. boundary box information. </ins>--[[User:Morgaine Dinova|Morgaine Dinova]] <ins style="font-weight: bold; text-decoration: none;">07</ins>:<ins style="font-weight: bold; text-decoration: none;">00</ins>, 25 September 2007 (PDT)</div></td></tr> <tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br></td></tr> <tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>* PS. Small point: note that '''edges''' of target regions are only a special (but common) case of region adjacency. A portal in particular can provide access directly into the interior of a target region, and in most case would do exactly that. --[[User:Morgaine Dinova|Morgaine Dinova]] 06:41, 25 September 2007 (PDT)</div></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>* PS. Small point: note that '''edges''' of target regions are only a special (but common) case of region adjacency. A portal in particular can provide access directly into the interior of a target region, and in most case would do exactly that. --[[User:Morgaine Dinova|Morgaine Dinova]] 06:41, 25 September 2007 (PDT)</div></td></tr> </table>

Morgaine Dinova https://wiki.secondlife.com/w/index.php?title=Talk:Central_Services&diff=32673&oldid=prev Morgaine Dinova at 13:48, 25 September 2007 2007-09-25T13:48:36Z

<p></p> <table style="background-color: #fff; color: #202122;" data-mw="interface"> <col class="diff-marker" /> <col class="diff-content" /> <col class="diff-marker" /> <col class="diff-content" /> <tr class="diff-title" lang="en"> <td colspan="2" style="background-color: #fff; color: #202122; text-align: center;">← Older revision</td> <td colspan="2" style="background-color: #fff; color: #202122; text-align: center;">Revision as of 06:48, 25 September 2007</td> </tr><tr><td colspan="2" class="diff-lineno" id="mw-diff-left-l22">Line 22:</td> <td colspan="2" class="diff-lineno">Line 22:</td></tr> <tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>: It's worth noting that the above approach may rapidly become obsolete, if it is not so already. The target region occupancy is not a large body of data in the context of today's machinery (only the per-object data really bloats it up), so it may be quite efficient for all occupancy data to be delivered in one fell swoop if the target region finds that best. In other words, the supplied relative coordinate is really only a heuristic hint to the target region. Certainly we don't want regions to be doing precision culling and clipping --- under the current static model, region servers don't scale, so this work '''must''' be done by the clients, which always scale linearly (or higher, with multicore). --[[User:Morgaine Dinova|Morgaine Dinova]] 06:24, 25 September 2007 (PDT)</div></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>: It's worth noting that the above approach may rapidly become obsolete, if it is not so already. The target region occupancy is not a large body of data in the context of today's machinery (only the per-object data really bloats it up), so it may be quite efficient for all occupancy data to be delivered in one fell swoop if the target region finds that best. In other words, the supplied relative coordinate is really only a heuristic hint to the target region. Certainly we don't want regions to be doing precision culling and clipping --- under the current static model, region servers don't scale, so this work '''must''' be done by the clients, which always scale linearly (or higher, with multicore). --[[User:Morgaine Dinova|Morgaine Dinova]] 06:24, 25 September 2007 (PDT)</div></td></tr> <tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br></td></tr> <tr><td class="diff-marker" data-marker="−"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #ffe49c; vertical-align: top; white-space: pre-wrap;"><div>* PS. Small point: note that '''edges''' of regions are only a special (but common) case of region adjacency. A portal in particular can provide access directly into the interior of a target region, and in most case would do exactly that. --[[User:Morgaine Dinova|Morgaine Dinova]] 06:41, 25 September 2007 (PDT)</div></td><td class="diff-marker" data-marker="+"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div>* PS. Small point: note that '''edges''' of <ins style="font-weight: bold; text-decoration: none;">target </ins>regions are only a special (but common) case of region adjacency. A portal in particular can provide access directly into the interior of a target region, and in most case would do exactly that. --[[User:Morgaine Dinova|Morgaine Dinova]] 06:41, 25 September 2007 (PDT)</div></td></tr> </table>

Morgaine Dinova https://wiki.secondlife.com/w/index.php?title=Talk:Central_Services&diff=32671&oldid=prev Morgaine Dinova at 13:41, 25 September 2007 2007-09-25T13:41:27Z

<p></p> <table style="background-color: #fff; color: #202122;" data-mw="interface"> <col class="diff-marker" /> <col class="diff-content" /> <col class="diff-marker" /> <col class="diff-content" /> <tr class="diff-title" lang="en"> <td colspan="2" style="background-color: #fff; color: #202122; text-align: center;">← Older revision</td> <td colspan="2" style="background-color: #fff; color: #202122; text-align: center;">Revision as of 06:41, 25 September 2007</td> </tr><tr><td colspan="2" class="diff-lineno" id="mw-diff-left-l21">Line 21:</td> <td colspan="2" class="diff-lineno">Line 21:</td></tr> <tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br></td></tr> <tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>: It's worth noting that the above approach may rapidly become obsolete, if it is not so already. The target region occupancy is not a large body of data in the context of today's machinery (only the per-object data really bloats it up), so it may be quite efficient for all occupancy data to be delivered in one fell swoop if the target region finds that best. In other words, the supplied relative coordinate is really only a heuristic hint to the target region. Certainly we don't want regions to be doing precision culling and clipping --- under the current static model, region servers don't scale, so this work '''must''' be done by the clients, which always scale linearly (or higher, with multicore). --[[User:Morgaine Dinova|Morgaine Dinova]] 06:24, 25 September 2007 (PDT)</div></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>: It's worth noting that the above approach may rapidly become obsolete, if it is not so already. The target region occupancy is not a large body of data in the context of today's machinery (only the per-object data really bloats it up), so it may be quite efficient for all occupancy data to be delivered in one fell swoop if the target region finds that best. In other words, the supplied relative coordinate is really only a heuristic hint to the target region. Certainly we don't want regions to be doing precision culling and clipping --- under the current static model, region servers don't scale, so this work '''must''' be done by the clients, which always scale linearly (or higher, with multicore). --[[User:Morgaine Dinova|Morgaine Dinova]] 06:24, 25 September 2007 (PDT)</div></td></tr> <tr><td colspan="2" class="diff-side-deleted"></td><td class="diff-marker" data-marker="+"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div><ins style="font-weight: bold; text-decoration: none;"></ins></div></td></tr> <tr><td colspan="2" class="diff-side-deleted"></td><td class="diff-marker" data-marker="+"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div><ins style="font-weight: bold; text-decoration: none;">* PS. Small point: note that '''edges''' of regions are only a special (but common) case of region adjacency. A portal in particular can provide access directly into the interior of a target region, and in most case would do exactly that. --[[User:Morgaine Dinova|Morgaine Dinova]] 06:41, 25 September 2007 (PDT)</ins></div></td></tr> </table>

Morgaine Dinova https://wiki.secondlife.com/w/index.php?title=Talk:Central_Services&diff=32669&oldid=prev Morgaine Dinova at 13:34, 25 September 2007 2007-09-25T13:34:34Z

<p></p> <table style="background-color: #fff; color: #202122;" data-mw="interface"> <col class="diff-marker" /> <col class="diff-content" /> <col class="diff-marker" /> <col class="diff-content" /> <tr class="diff-title" lang="en"> <td colspan="2" style="background-color: #fff; color: #202122; text-align: center;">← Older revision</td> <td colspan="2" style="background-color: #fff; color: #202122; text-align: center;">Revision as of 06:34, 25 September 2007</td> </tr><tr><td colspan="2" class="diff-lineno" id="mw-diff-left-l20">Line 20:</td> <td colspan="2" class="diff-lineno">Line 20:</td></tr> <tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>: The information returned is not necessarily culled as a function of distance either: for example, a mountain on the far side of a region would become visible even when you approach the near side. It still needs to be presented to the agent for passing to the client as proxy and/or sent directly to the client. Despite the large topological distance to the mountain, a modern client will still display the remote entity, with CLOD and other techniques manipulating the rendering resolution appropriately.</div></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>: The information returned is not necessarily culled as a function of distance either: for example, a mountain on the far side of a region would become visible even when you approach the near side. It still needs to be presented to the agent for passing to the client as proxy and/or sent directly to the client. Despite the large topological distance to the mountain, a modern client will still display the remote entity, with CLOD and other techniques manipulating the rendering resolution appropriately.</div></td></tr> <tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br></td></tr> <tr><td class="diff-marker" data-marker="−"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #ffe49c; vertical-align: top; white-space: pre-wrap;"><div>: It's worth <del style="font-weight: bold; text-decoration: none;">nothing </del>that the above approach may rapidly become obsolete, if it is not so already. The target region occupancy is not a large body of data in the context of today's machinery (only the per-object data really bloats it up), so it may be quite efficient for all occupancy data to be delivered in one fell swoop if the target region finds that best. In other words, the supplied relative coordinate is really only a heuristic hint to the target region. Certainly we don't want regions to be doing precision culling and clipping --- under the current static model, region servers don't scale, so this work '''must''' be done by the clients, which always scale linearly (or higher, with multicore). --[[User:Morgaine Dinova|Morgaine Dinova]] 06:24, 25 September 2007 (PDT)</div></td><td class="diff-marker" data-marker="+"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div>: It's worth <ins style="font-weight: bold; text-decoration: none;">noting </ins>that the above approach may rapidly become obsolete, if it is not so already. The target region occupancy is not a large body of data in the context of today's machinery (only the per-object data really bloats it up), so it may be quite efficient for all occupancy data to be delivered in one fell swoop if the target region finds that best. In other words, the supplied relative coordinate is really only a heuristic hint to the target region. Certainly we don't want regions to be doing precision culling and clipping --- under the current static model, region servers don't scale, so this work '''must''' be done by the clients, which always scale linearly (or higher, with multicore). --[[User:Morgaine Dinova|Morgaine Dinova]] 06:24, 25 September 2007 (PDT)</div></td></tr> </table>

Morgaine Dinova https://wiki.secondlife.com/w/index.php?title=Talk:Central_Services&diff=32668&oldid=prev Morgaine Dinova at 13:33, 25 September 2007 2007-09-25T13:33:11Z

<p></p> <table style="background-color: #fff; color: #202122;" data-mw="interface"> <col class="diff-marker" /> <col class="diff-content" /> <col class="diff-marker" /> <col class="diff-content" /> <tr class="diff-title" lang="en"> <td colspan="2" style="background-color: #fff; color: #202122; text-align: center;">← Older revision</td> <td colspan="2" style="background-color: #fff; color: #202122; text-align: center;">Revision as of 06:33, 25 September 2007</td> </tr><tr><td colspan="2" class="diff-lineno" id="mw-diff-left-l16">Line 16:</td> <td colspan="2" class="diff-lineno">Line 16:</td></tr> <tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br></td></tr> <tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>* Adding a bit more to "Tell me what an agent looking into your region from relative coordinate X.Y.Z needs to know":</div></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>* Adding a bit more to "Tell me what an agent looking into your region from relative coordinate X.Y.Z needs to know":</div></td></tr> <tr><td class="diff-marker" data-marker="−"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #ffe49c; vertical-align: top; white-space: pre-wrap;"><div>: Note that it's not functionally any different making these requests from inside or outside of that region --- both types of request need a source coordinate reference for spatial relevance sorting. As you say, only the relative coordinate w.r.to the target region's space really matters, not the absolute coordinate within the requesting region. Indeed, given that portal apertures can be moved around at will, and even animated, it would be a mistake to require the target region to perform the required mapping on each request: let the requester suffer the overhead of being overly clever, <del style="font-weight: bold; text-decoration: none;">and </del>always <del style="font-weight: bold; text-decoration: none;">supply </del>the needed relative coordinate on each request.</div></td><td class="diff-marker" data-marker="+"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div>: Note that it's not functionally any different making these requests from inside or outside of that region --- both types of request need a source coordinate reference for spatial relevance sorting. As you say, only the relative coordinate w.r.to the target region's space really matters, not the absolute coordinate within the requesting region. Indeed, given that portal apertures can be moved around at will, and even animated, it would be a mistake to require the target region to perform the required mapping on each request: let the requester suffer the overhead of being overly clever, <ins style="font-weight: bold; text-decoration: none;">so </ins>always <ins style="font-weight: bold; text-decoration: none;">compute </ins>the needed <ins style="font-weight: bold; text-decoration: none;">''</ins>relative<ins style="font-weight: bold; text-decoration: none;">'' </ins>coordinate on each request.</div></td></tr> <tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br></td></tr> <tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>: The information returned is not necessarily culled as a function of distance either: for example, a mountain on the far side of a region would become visible even when you approach the near side. It still needs to be presented to the agent for passing to the client as proxy and/or sent directly to the client. Despite the large topological distance to the mountain, a modern client will still display the remote entity, with CLOD and other techniques manipulating the rendering resolution appropriately.</div></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>: The information returned is not necessarily culled as a function of distance either: for example, a mountain on the far side of a region would become visible even when you approach the near side. It still needs to be presented to the agent for passing to the client as proxy and/or sent directly to the client. Despite the large topological distance to the mountain, a modern client will still display the remote entity, with CLOD and other techniques manipulating the rendering resolution appropriately.</div></td></tr> <tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br></td></tr> <tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>: It's worth nothing that the above approach may rapidly become obsolete, if it is not so already. The target region occupancy is not a large body of data in the context of today's machinery (only the per-object data really bloats it up), so it may be quite efficient for all occupancy data to be delivered in one fell swoop if the target region finds that best. In other words, the supplied relative coordinate is really only a heuristic hint to the target region. Certainly we don't want regions to be doing precision culling and clipping --- under the current static model, region servers don't scale, so this work '''must''' be done by the clients, which always scale linearly (or higher, with multicore). --[[User:Morgaine Dinova|Morgaine Dinova]] 06:24, 25 September 2007 (PDT)</div></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>: It's worth nothing that the above approach may rapidly become obsolete, if it is not so already. The target region occupancy is not a large body of data in the context of today's machinery (only the per-object data really bloats it up), so it may be quite efficient for all occupancy data to be delivered in one fell swoop if the target region finds that best. In other words, the supplied relative coordinate is really only a heuristic hint to the target region. Certainly we don't want regions to be doing precision culling and clipping --- under the current static model, region servers don't scale, so this work '''must''' be done by the clients, which always scale linearly (or higher, with multicore). --[[User:Morgaine Dinova|Morgaine Dinova]] 06:24, 25 September 2007 (PDT)</div></td></tr> </table>

Morgaine Dinova https://wiki.secondlife.com/w/index.php?title=Talk:Central_Services&diff=32667&oldid=prev Morgaine Dinova at 13:31, 25 September 2007 2007-09-25T13:31:24Z

<p></p> <table style="background-color: #fff; color: #202122;" data-mw="interface"> <col class="diff-marker" /> <col class="diff-content" /> <col class="diff-marker" /> <col class="diff-content" /> <tr class="diff-title" lang="en"> <td colspan="2" style="background-color: #fff; color: #202122; text-align: center;">← Older revision</td> <td colspan="2" style="background-color: #fff; color: #202122; text-align: center;">Revision as of 06:31, 25 September 2007</td> </tr><tr><td colspan="2" class="diff-lineno" id="mw-diff-left-l15">Line 15:</td> <td colspan="2" class="diff-lineno">Line 15:</td></tr> <tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>- Zha Ewry 9-25-2007</div></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>- Zha Ewry 9-25-2007</div></td></tr> <tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br></td></tr> <tr><td class="diff-marker" data-marker="−"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #ffe49c; vertical-align: top; white-space: pre-wrap;"><div>* <del style="font-weight: bold; text-decoration: none;">Re </del>"Tell me what an agent looking into your region from relative coordinate X.Y.Z needs to know":</div></td><td class="diff-marker" data-marker="+"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div>* <ins style="font-weight: bold; text-decoration: none;">Adding a bit more to </ins>"Tell me what an agent looking into your region from relative coordinate X.Y.Z needs to know":</div></td></tr> <tr><td class="diff-marker" data-marker="−"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #ffe49c; vertical-align: top; white-space: pre-wrap;"><div>: <del style="font-weight: bold; text-decoration: none;">The agent just needs access to the objects with which the client can build a scene graph of the desired region, so </del>it's not functionally any different making these requests from inside or outside of that region --- both types of request need a source coordinate reference for spatial relevance sorting. <del style="font-weight: bold; text-decoration: none;">Geometrically</del>, only the relative coordinate w.r.to the target region's space really matters, not the absolute coordinate within the requesting region. Indeed, given that portal apertures can be moved around at will, and even animated, it would be a mistake to require the target region to perform the required mapping on each request: let the requester suffer the overhead of being overly clever, and always supply the needed relative coordinate on each request.</div></td><td class="diff-marker" data-marker="+"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div>: <ins style="font-weight: bold; text-decoration: none;">Note that </ins>it's not functionally any different making these requests from inside or outside of that region --- both types of request need a source coordinate reference for spatial relevance sorting. <ins style="font-weight: bold; text-decoration: none;">As you say</ins>, only the relative coordinate w.r.to the target region's space really matters, not the absolute coordinate within the requesting region. Indeed, given that portal apertures can be moved around at will, and even animated, it would be a mistake to require the target region to perform the required mapping on each request: let the requester suffer the overhead of being overly clever, and always supply the needed relative coordinate on each request.</div></td></tr> <tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br></td></tr> <tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>: The information returned is not necessarily culled as a function of distance either: for example, a mountain on the far side of a region would become visible even when you approach the near side. It still needs to be presented to the agent for passing to the client as proxy and/or sent directly to the client. Despite the large topological distance to the mountain, a modern client will still display the remote entity, with CLOD and other techniques manipulating the rendering resolution appropriately.</div></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>: The information returned is not necessarily culled as a function of distance either: for example, a mountain on the far side of a region would become visible even when you approach the near side. It still needs to be presented to the agent for passing to the client as proxy and/or sent directly to the client. Despite the large topological distance to the mountain, a modern client will still display the remote entity, with CLOD and other techniques manipulating the rendering resolution appropriately.</div></td></tr> <tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br></td></tr> <tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>: It's worth nothing that the above approach may rapidly become obsolete, if it is not so already. The target region occupancy is not a large body of data in the context of today's machinery (only the per-object data really bloats it up), so it may be quite efficient for all occupancy data to be delivered in one fell swoop if the target region finds that best. In other words, the supplied relative coordinate is really only a heuristic hint to the target region. Certainly we don't want regions to be doing precision culling and clipping --- under the current static model, region servers don't scale, so this work '''must''' be done by the clients, which always scale linearly (or higher, with multicore). --[[User:Morgaine Dinova|Morgaine Dinova]] 06:24, 25 September 2007 (PDT)</div></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>: It's worth nothing that the above approach may rapidly become obsolete, if it is not so already. The target region occupancy is not a large body of data in the context of today's machinery (only the per-object data really bloats it up), so it may be quite efficient for all occupancy data to be delivered in one fell swoop if the target region finds that best. In other words, the supplied relative coordinate is really only a heuristic hint to the target region. Certainly we don't want regions to be doing precision culling and clipping --- under the current static model, region servers don't scale, so this work '''must''' be done by the clients, which always scale linearly (or higher, with multicore). --[[User:Morgaine Dinova|Morgaine Dinova]] 06:24, 25 September 2007 (PDT)</div></td></tr> </table>

Morgaine Dinova https://wiki.secondlife.com/w/index.php?title=Talk:Central_Services&diff=32666&oldid=prev Morgaine Dinova at 13:29, 25 September 2007 2007-09-25T13:29:29Z

<p></p> <table style="background-color: #fff; color: #202122;" data-mw="interface"> <col class="diff-marker" /> <col class="diff-content" /> <col class="diff-marker" /> <col class="diff-content" /> <tr class="diff-title" lang="en"> <td colspan="2" style="background-color: #fff; color: #202122; text-align: center;">← Older revision</td> <td colspan="2" style="background-color: #fff; color: #202122; text-align: center;">Revision as of 06:29, 25 September 2007</td> </tr><tr><td colspan="2" class="diff-lineno" id="mw-diff-left-l20">Line 20:</td> <td colspan="2" class="diff-lineno">Line 20:</td></tr> <tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>: The information returned is not necessarily culled as a function of distance either: for example, a mountain on the far side of a region would become visible even when you approach the near side. It still needs to be presented to the agent for passing to the client as proxy and/or sent directly to the client. Despite the large topological distance to the mountain, a modern client will still display the remote entity, with CLOD and other techniques manipulating the rendering resolution appropriately.</div></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>: The information returned is not necessarily culled as a function of distance either: for example, a mountain on the far side of a region would become visible even when you approach the near side. It still needs to be presented to the agent for passing to the client as proxy and/or sent directly to the client. Despite the large topological distance to the mountain, a modern client will still display the remote entity, with CLOD and other techniques manipulating the rendering resolution appropriately.</div></td></tr> <tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br></td></tr> <tr><td class="diff-marker" data-marker="−"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #ffe49c; vertical-align: top; white-space: pre-wrap;"><div>: It's worth nothing that the above approach may rapidly <del style="font-weight: bold; text-decoration: none;">because </del>obsolete, if it is not so already. The target region occupancy is not a large body of data in the context of today's machinery (only the per-object data really bloats it up), so it may be quite efficient for all occupancy data to be delivered in one fell swoop if the target region finds that best. In other words, the supplied relative coordinate is really only a heuristic hint to the target region. Certainly we don't want regions to be doing precision culling and clipping --- under the current static model, region servers don't scale, so this work '''must''' be done by the clients, which always scale linearly (or higher, with multicore). --[[User:Morgaine Dinova|Morgaine Dinova]] 06:24, 25 September 2007 (PDT)</div></td><td class="diff-marker" data-marker="+"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div>: It's worth nothing that the above approach may rapidly <ins style="font-weight: bold; text-decoration: none;">become </ins>obsolete, if it is not so already. The target region occupancy is not a large body of data in the context of today's machinery (only the per-object data really bloats it up), so it may be quite efficient for all occupancy data to be delivered in one fell swoop if the target region finds that best. In other words, the supplied relative coordinate is really only a heuristic hint to the target region. Certainly we don't want regions to be doing precision culling and clipping --- under the current static model, region servers don't scale, so this work '''must''' be done by the clients, which always scale linearly (or higher, with multicore). --[[User:Morgaine Dinova|Morgaine Dinova]] 06:24, 25 September 2007 (PDT)</div></td></tr> </table>

Morgaine Dinova