I think this is just why the module architecture is a great thing, to allow us to differ from SL in terms of policy and architecture as we see fit without breaking compatibility.<br><br>Cheers,<br>James aka Twitch/Hiro<br>
<br><br><div class="gmail_quote">On Dec 19, 2007 10:43 AM, Stefan Andersson <<a href="mailto:stefan@tribalmedia.se">stefan@tribalmedia.se</a>> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div>On a side note, this is also implemented in the Reg Api that third parties can use to auto-register their members onto SL; there is an option to confine the newly registered user account to an estate owned by the registrator; ie to create a 'walled garden' within SL.
<br>
<br>
/Stefan<br><br><br><br><br>
<blockquote>
<hr>
Date: Wed, 19 Dec 2007 11:21:10 -0500<br>From: <a href="mailto:teravus@gmail.com" target="_blank">teravus@gmail.com</a><br>To: <a href="mailto:opensim-dev@lists.berlios.de" target="_blank">opensim-dev@lists.berlios.de</a>
<br>Subject: Re: [Opensim-dev] Why we shouldnt support Estates<div><div></div><div class="Wj3C7c"><br><br>
<div>There's another purpose for estates also. </div>
<div>Grid separation, on the same infrastructure.</div>
<div> </div>
<div>The EstateID, and ParentEstateID Property</div>
<div> </div>
<div>Basically, this is what LL uses to separate the MainGrid from the Teen Grid while not significantly increasing the hardware or configuration requirements.</div>
<div> </div>
<div>All Users have a EstateID Property.. that corresponds to the regions and users that they can interact with and see.<br> </div>
<div>Example</div>
<div>*One main grid has an estateID 0. All users to this grid are created with an estateID 0 property.</div>
<div> </div>
<div>*A teen grid has an estateID 2. All users who sign up for this grid are created with an estateID 2</div>
<div><br>When users pull up the map, they can only see the regions where the EstateID or the ParentEstateID = their user estateID property.</div>
<div> </div>
<div>This also extends to Instant Messages and teleports.</div>
<div> </div>
<div>'God Users' can see, interact with, and move in between all EstateIDs</div>
<div> </div>
<div>I can see this being used by a service provider to give users their own 'grid'. </div>
<div> </div>
<div>My purpose for mentioning this is to make sure that this functionality is considered, *not to rehash the idea of estates*</div>
<div> </div>
<div> </div>
<div><span>On 12/19/07, <b>Adam Frisby</b> <<a href="mailto:adam@gwala.net" target="_blank">adam@gwala.net</a>> wrote:</span>
<blockquote style="border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">Pardoning the slightly inflamatory subject line - allow me to clarify.<br><br>The "Estate" system as currently implemented by Linden Lab is shall we
<br>say ... imperfect?<br><br>Right now -- as it stands, an estate is a collection of regions under a<br>common name sharing a few properties:<br><br> * Estate Owner is shared across all regions in the estate<br> * Estate Managers are shared across all regions in the estate
<br> * Estate Bans are shared across the estate<br> * The time-of-day is shared across all regions in the estate<br><br>Frankly - I think this is mediocre at best, very limiting at worst.<br><br>For example, say you have two seperate groups of regions that want to
<br>share a single ban list? RBL's seem to indicate people will want to do this.<br><br>So - what's the solution? Remove abitrary groupings and make each of<br>these something independently configurable, for example:
<br><br> Ban List<br> Rather than have a single list shared among X regions,<br> allow regions to be configured to have a remote banlist<br> - some kind of URL where they can POST / GET queries
<br> about user status. Put this functionality into a<br> BanModule-type RegionModule so it can be swapped or<br> configured independently at whim.<br><br> Estate Managers<br>
Similar to the above, add support in the permission<br> manager for looking up the permissions of a individual<br> user from a remote URL or address.<br><br>Now, the PermissionsModule and BanModule should respond to messages from
<br>the client sent by the estate tools -- but on the backend we have a much<br>more configurable situation which is more suitable for large scale<br>deployments.<br><br>Regards,<br><br>Adam<br>_______________________________________________
<br>Opensim-dev mailing list<br><a href="mailto:Opensim-dev@lists.berlios.de" target="_blank">Opensim-dev@lists.berlios.de</a><br><a href="https://lists.berlios.de/mailman/listinfo/opensim-dev" target="_blank">https://lists.berlios.de/mailman/listinfo/opensim-dev
</a><br></blockquote></div><br></div></div></blockquote></div>
<br>_______________________________________________<br>Opensim-dev mailing list<br><a href="mailto:Opensim-dev@lists.berlios.de">Opensim-dev@lists.berlios.de</a><br><a href="https://lists.berlios.de/mailman/listinfo/opensim-dev" target="_blank">
https://lists.berlios.de/mailman/listinfo/opensim-dev</a><br><br></blockquote></div><br><br clear="all"><br>-- <br>===================================<br>The wind<br>scours the earth for prayers<br>The night obscures them