I basically mean case 2, case 1 is good, but foreign user approach doesn't fit every use case. For instance some grids/regions might want to be "walled grids". But that doesn't mean a user shouldn't be able to bring his inventory and assets if they want (and the grid allows). So we need to support a user registering multiple accounts but using a single inventory set (not different sets for each account). <br> <br> But as well as registering multiple accounts, there are other use cases that require the multiple user server/grids accessing a single inventory set. We (tribalnet) have such a system, in that there is a global grid mode, but also a private build mode. build mode is basically a adapted standalone region with its own user server. But each user has the same userid on it as in the global grid. Both modes also share the same asset and inventory servers. So anything you upload/ or create in build mode will be avaliable when you login to the grid.<br><br>I see it as a
requirement that this sort of thing isn't broke. We should always think that different people have different use cases. And have to allow them. Certainly if its possible now, then we shouldn't do changes that break it.<br><br><b><i>liu xiaolu <lulurun@gmail.com></i></b> wrote:<blockquote class="replbq" style="border-left: 2px solid rgb(16, 16, 255); margin-left: 5px; padding-left: 5px;"> <div dir="ltr">>If you have an userserver url in some db in the inventory server, then this needs updating when a user changes grids<br><br>this depends on what exactly "change grid" means:<br><br>1. if it means user registers at GridService1 and want to login to a regionserver at GridService2, THEN<br> That is my point, and I think that is the point maybe I did described clearly:<br>just for "grid jump", *** user need not to change its grids(here means userserver_url)***<br>user can only register in one gridservice(userserver), and he can keep its account there forever, and the
user still can travel to other gridservices.<br> [avatar portability mechanism:]<br>because when the an user login to a "foreign region" in other gridservice<br>* the user tells the "foreign region" to claim its identity from its original userserver.<br> * the user tells the "foreign region" to bring its belongings into the world(appearance, inventory).<br>In this case "userserver_dictionary" *need not to be updated*<br><br>2. if it means: user register another account at another gridservice. like today I have been using hotmail, and now I am using gmail. THEN<br> * if the user cares about his/her belongings, by using the portability mechanism I methioned in 1, the user can still use his/her previous<br> inventory/asset service, because inventory/asset server are independent., in this case, yes, "userserver_dictionary" *need to be updated*,<br> (to set userserver_url point to current userservice) but this kind of "change" won't be frequent, like today, how
many free mail accounts<br> are you "really" using, or how many times you changes your mail account ?<br> <div class="gmail_quote">* if the user want to start a new life, maybe he/she does not mind start from "zero", like today I switch to gmail, I can not read my past<br> mails in hotmail in gmail. why I change to gmail? because my hotmail is full with spam, I donot want to clean it.<br><br>regards,<br>lulurun<br><br>2008/7/25 Michael Wright <<a href="mailto:michaelwri22@yahoo.co.uk">michaelwri22@yahoo.co.uk</a>>:<br> <blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Well no, as each user should have a inventory server url in their userprofile db. So that is looked up and the login server then asks for permission on the inventory server to access a users inventory and to push the session id. So yes you need to set up permissions on the inventory server to allow the various
"grids" to access a users inventory. <br> <br>But as there could be multiple grids authorised for a user, it allows the user to login and out of those grids while keeping the same inventory. If you have a userserver url in some db in the inventory server, then this needs updating when a user changes grids (or if multiple urls were saved, then the active one needs setting). And it certainly shouldn't have to be done manually so again it requires a push. <br> <div class="Ih2E3d"><br><b><i>liu xiaolu <<a href="mailto:lulurun@gmail.com" target="_blank">lulurun@gmail.com</a>></i></b> wrote:</div><div class="Ih2E3d"><blockquote style="border-left: 2px solid rgb(16, 16, 255); margin-left: 5px; padding-left: 5px;"> <div dir="ltr">Comparing "pull" and "push", I would like to say:<br>pull is "require setting a lot of urls on different servers anyway", but push is full with vulnerability.<br><br></div></blockquote><br></div><div> </div><hr size="1"><div
class="Ih2E3d"> Not happy with your email address? <br> <a href="http://uk.docs.yahoo.com/ymail/new.html" target="_blank"> Get the one you really want</a> - millions of new email addresses available now at <a href="http://uk.docs.yahoo.com/ymail/new.html" target="_blank"> Yahoo!</a></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>Lulurun </div> _______________________________________________<br>Opensim-dev mailing list<br>Opensim-dev@lists.berlios.de<br>https://lists.berlios.de/mailman/listinfo/opensim-dev<br></blockquote><br><p>
<hr size=1>
Not happy with your email address?
<br> <a href="http://uk.docs.yahoo.com/ymail/new.html"> Get the one you
really want</a> - millions of new email addresses available now at <a
href="http://uk.docs.yahoo.com/ymail/new.html"> Yahoo!</a>