When I first mentioned XMPP it was just a throw out idea. But thinking and looking into it some more I actually think its got some plus points. But I don't think we should think about it for Assets (which I think REST is the correct thing for) and maybe not even inventory. I was thinking more User server and grid server. <br><br>I really don't think using REST because thats what LL use makes any difference as when they release specs we are going to have to have new implementation anyway. Please remember not everyone is interested in connecting to LL grid, so I think no matter what happens it most likely will be, that we end up with at least two implementations; our own and one compatible with their grid. <br><br>I think XMPP most likely will end up as easiest and fastest to implement and it includes a number of things that we wouldn't need to spend time on. But when it comes down to it, I'm not fixed on the idea enough to fight strongly for it. So if the general opinion is
for REST for all. Then I'd go with that without a problem. As long as we are going with it for the right reasons and not the compatible reason.<br><br><br><b><i>Sean Dague <sean@dague.net></i></b> wrote:<blockquote class="replbq" style="border-left: 2px solid rgb(16, 16, 255); margin-left: 5px; padding-left: 5px;"> On Sat, Nov 03, 2007 at 12:26:30AM +0800, Adam Frisby wrote:<br>> Following on from the previous grid standards email, we should now look <br>> at what we need to revise and propose some actual hard specifications <br>> that we can use.<br>> <br>> Some base guidelines:<br>> * No EventQueueGet or anything similar. If it needs speed, make sure we <br>> can specify something like a remoting serialiser and use TCP sockets for <br>> this.<br>> * Re-use existing standards and libraries where possible. No creation of <br>> unnessecary standards without good justification (ie LLSD vs JSON)<br><br>++++++++ (I think I've run out of
pluses.) Can't agree enough on this point.<br><br>> MW has suggested we look at using XMPP for this - from my cursory <br>> examination this looks like a reasonable protocol that we could actually <br>> use for at least things like handshaking and core [inter]grid<br>> protocols.<br><br>After spending some time tracing on Tleiades AssetServer, based on REST,<br>REST has my vote. The flexibility to get data in and our of the<br>environment is really nice.<br><br>The other nice things with REST is that HTTP load balancing techniques<br>are fairly well understood in the industry. For instance, there are<br>even techniques and products for session aware HTTP spreaders. It also<br>has the advantage of being similar to the aproach Zero has stated the<br>Linden grid is moving in, so future interop with the Linden grid will be<br>easier if our base services are REST.<br><br>That being said, I'd really like to see XMPP integration for IM if<br>possible, as it will
make for easy bridging of in world presence to out<br>of world IM systems.<br><br>> The core grid functionality (what needs defining - this list will need <br>> to grow, currently just including things we use)<br>> <br>> -- What needs defining --<br><br>I assume all the User & Agent services are Region <-> Grid Server(s)?<br>Please correct me if I'm being dumb here.<br><br>> * User Services [grouped together]<br>> ** Profile Retrieval<br>> ** Instant Messaging --> Move to client?<br>> ** Inventory Handling --> Move to client?<br>> * List Inventory --> Move to client?<br>> * Rez Inventory Item --> Move to client?<br><br>Can you define move to client? in this context?<br><br>> ** User Login to Grid<br>> <br>> * Agent Services [grouped together]<br>> ** Session Retrieval<br>> ** Session Authentication<br><br>Both of those are Region <-> Agent Server for user info?<br><br>> ** Region Login from
Grid<br><br>This is the circuit setup?<br><br>> * Region Services [grouped together]<br>> ** Region Information Retrieval<br>> ** World Map Services<br>> ** ID/Position to URI translation<br><br>I'm not sure I fully understand what all the functions in each of these<br>are, can you explain a bit more?<br><br>This is a really great post, btw, in clarifying what it is that we need<br>to start defining. Thanks for getting this out here Adam.<br><br> -Sean<br><br>-- <br>__________________________________________________________________<br><br>Sean Dague Mid-Hudson Valley<br>sean at dague dot net Linux Users Group<br>http://dague.net http://mhvlug.org<br><br>There is no silver bullet. Plus, werewolves make better neighbors<br>than zombies, and they tend to keep the vampire population
down.<br>__________________________________________________________________<br>_______________________________________________<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>
For ideas on reducing your carbon footprint visit <a href="http://uk.promotions.yahoo.com/forgood/environment.html">Yahoo! For Good</a> this month.