<html><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">Yep -- that is all part of protocol design, the fun part :) <div><br><div>With this new software architecture you can instantiate your handler with whatever service references you need, so you can do whatever additional functional bits you need for your protocol. For example, if you need to create/retrieve accounts, have your handler either get or create an IUserAccountService object. </div><div><br></div><div>When you get to this point in your rewrite, if you need help let me know, and I can explain better how to get service connectors to the handlers themselves.</div><div><br></div><div><div><br><div><div>On Jan 7, 2010, at 2:01 PM, David W Levine wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><br><font size="2" face="sans-serif">There's an interesting thought lurking there. Some of these choices are going to be made by the grid builders,</font> <br><font size="2" face="sans-serif">not the protocol builders. I think, in a *lot* of cases, Meadhbh is right. The visiting avatar's home grid will</font> <br><font size="2" face="sans-serif">be holding inventory and assets will be scattered on services as that grid (and possibly user) chooses.</font> <br> <br><font size="2" face="sans-serif">That said, nothing prevents a region from allowing its users to say "Hey, Jacob <a href="mailto:SillyAvatarName@Grid1.vwcompany.com">SillyAvatarName@Grid1.vwcompany.com</a>" should</font> <br><font size="2" face="sans-serif">be managed persistently here in a relationship with "Jacob <a href="mailto:Smith@localGrid.vwfreegrid.org">Smith@localGrid.vwfreegrid.org</a>" my identity here. I'm strongly in favor</font> <br><font size="2" face="sans-serif">of delegating as many of these choices as possible to the grids, and the services they deploy and trying very hard to prejudge</font> <br><font size="2" face="sans-serif">what the grid creators and ultimately end users will want. </font> <br> <br><font size="2" face="sans-serif">- David / Zha</font> <br> <br> <br><tt><font size="2"><a href="mailto:opensim-dev-bounces@lists.berlios.de">opensim-dev-bounces@lists.berlios.de</a> wrote on 01/07/2010 04:55:25 PM:<br> <br> > [image removed] </font></tt> <br><tt><font size="2">> <br> > Re: [Opensim-dev] OGP module and the grand re-factor...</font></tt> <br><tt><font size="2">> <br> > Melanie </font></tt> <br><tt><font size="2">> <br> > to:</font></tt> <br><tt><font size="2">> <br> > opensim-dev</font></tt> <br><tt><font size="2">> <br> > 01/07/2010 04:55 PM</font></tt> <br><tt><font size="2">> <br> > Sent by:</font></tt> <br><tt><font size="2">> <br> > <a href="mailto:opensim-dev-bounces@lists.berlios.de">opensim-dev-bounces@lists.berlios.de</a></font></tt> <br><tt><font size="2">> <br> > Please respond to opensim-dev</font></tt> <br><tt><font size="2">> <br> > Hi,<br> > <br> > the other night, Meadhbh told me that the persistent accounts were<br> > not intended. So that's cleared up.<br> > <br> > Melanie<br> > <br> > Cristina Videira Lopes wrote:<br> > > David,<br> > > <br> > > With this latest refactoring came the new Simulation service, <br> > > represented by ISimulationService. Please take a look at it. The data <br> > > structures that it currently takes for creating and updating agents <br> > > are still incomplete (one of them needs more data for foreign users), <br> > > but I think you'll get the idea very quickly. We may be able to come <br> > > up with the basic common data, and then have more specialized data <br> > > structures for each agent transfer protocol.<br> > > <br> > > I took a look at the OGP module the other day, and it really looked to <br> > > me like it can be written as an alternative handler that receives/ <br> > > sends the data from/to the wire using the specific protocol that you <br> > > guys have been cooking, but that calls the existing simulation service <br> > > exactly like the existing handler. The existing handler is in <br> > > OpenSim.Server.Handlers.Simulation.<br> > > <br> > > There were several important details that you obviously need to make <br> > > decisions upon, like -- do you really want to create a persistent <br> > > account for foreign users? etc. As I was about to do the rewrite of <br> > > that module for the new services, it was obvious that I couldn't make <br> > > that call, or I would be designing OGP myself :)<br> > > <br> > > As I was hoping, I think this will be an excellent vehicle to discuss <br> > > similarities and differences between OGP and HG and any other agent <br> > > transfer protocols out there.<br> > > <br> > > Crista / Diva<br> > > <br> > > On Jan 7, 2010, at 1:29 PM, David W Levine wrote:<br> > > <br> > >><br> > >> There's a more recent copy on the github repository linked to out of <br> > >> gridforge. (gridforge still being SVN is... a wee challange) The <br> > >> tree there is a light fork off<br> > >> of September. There are a couple of changes which permit inventory <br> > >> to run from caps hosted by the Agent Service in that tree, as well <br> > >> as some code to manage<br> > >> reflecting region inventory interactions to the Agent Service. <br> > >> git://github.com/zekizeki/agentservice.git That should be current.<br> > >><br> > >> I've been giving the right way to sync up a bit of thought. I <br> > >> suspect that the OGP module really wants to be built at a different <br> > >> layer in the post re-factor world, probably<br> > >> as a service, using the connectors to talk to the rest of the system <br> > >> like any other well behaved component. The basic task of the OGP <br> > >> code is to parse the request from<br> > >> a remote Agent Service, decide whether to accept it or not, and <br> > >> then, setup the region to welcome the client. Currently the OGP code <br> > >> stuff things into the region with a bit<br> > >> of a sledghammer. I'd think doing it properly, with connectors would <br> > >> be much nicer for everyone, and isolate the code properly. I suspect <br> > >> the biggest tricky bit is whether<br> > >> the right bits are exposed to have the region ready to talk to the <br> > >> client with the right agentID, secure Circuit ID, and a properly <br> > >> setup user agent to match. I'll start looking<br> > >> at that in the current connector code.<br> > >><br> > >> Overall, the connector approach, and getting as many of the services <br> > >> decoupled is clearly the way to go, especially, if we want to allow <br> > >> everyone to explore a range of<br> > >> messaging, inventory and asset serving models over the next chunk of <br> > >> grid evolution. I'm hopeful we can start getting some really useful <br> > >> evolution to happen pairwise in the<br> > >> clients and the services this year, which should make everyone's <br> > >> life more flexible.<br> > >><br> > >> - David<br> > >><br> > >><br> > >><br> > >> <a href="mailto:opensim-dev-bounces@lists.berlios.de">opensim-dev-bounces@lists.berlios.de</a> wrote on 01/06/2010 01:14:32 PM:<br> > >><br> > >> > [image removed]<br> > >> ><br> > >> > Re: [Opensim-dev] OGP module and the grand re-factor...<br> > >> ><br> > >> > diva<br> > >> ><br> > >> > to:<br> > >> ><br> > >> > opensim-dev<br> > >> ><br> > >> > 01/06/2010 01:14 PM<br> > >> ><br> > >> > Sent by:<br> > >> ><br> > >> > <a href="mailto:opensim-dev-bounces@lists.berlios.de">opensim-dev-bounces@lists.berlios.de</a><br> > >> ><br> > >> > Please respond to diva, opensim-dev<br> > >> ><br> > >> > Hi David,<br> > >> ><br> > >> > First question is: what's the most updated version of OGP? Is it <br> > >> what's<br> > >> > currently in the core distro, or do you have something more recent<br> > >> > somewhere else?<br> > >> ><br> > >> > Diva / Crista<br> > >> ><br> > >> > David W Levine wrote:<br> > >> > ><br> > >> > > I gather the current grand refactoring is washing up on the <br> > >> shores of<br> > >> > > the OGP module (which is hardly surprising) So, I'll raise my <br> > >> hand and<br> > >> > > say "I'll make sure it gets sorted out" I gather Melanie and <br> > >> DIva are<br> > >> > > looking<br> > >> > > for that hand raise, so here it is. Since I'm also about to look <br> > >> at<br> > >> > > adding in X.509 based counterpart validation to the code this <br> > >> month,<br> > >> > > I'll be in there anyway. So... Lets sort out what's needed to <br> > >> make this<br> > >> > > as painless as<br> > >> > > possible for everyone.<br> > >> > ><br> > >> > ><br> > >> > ><br> > >> > > - David / Zha<br> > >> > ><br> > >> > ><br> > >> > > <br> > >> ------------------------------------------------------------------------<br> > >> > ><br> > >> > > _______________________________________________<br> > >> > > Opensim-dev mailing list<br> > >> > > <a href="mailto:Opensim-dev@lists.berlios.de">Opensim-dev@lists.berlios.de</a><br> > >> > > </font></tt><a href="https://lists.berlios.de/mailman/listinfo/opensim-dev"><tt><font size="2">https://lists.berlios.de/mailman/listinfo/opensim-dev</font></tt></a><tt><font size="2"><br> > >> > _______________________________________________<br> > >> > Opensim-dev mailing list<br> > >> > <a href="mailto:Opensim-dev@lists.berlios.de">Opensim-dev@lists.berlios.de</a><br> > >> > </font></tt><a href="https://lists.berlios.de/mailman/listinfo/opensim-dev"><tt><font size="2">https://lists.berlios.de/mailman/listinfo/opensim-dev</font></tt></a><tt><font size="2"><br> > >> _______________________________________________<br> > >> Opensim-dev mailing list<br> > >> <a href="mailto:Opensim-dev@lists.berlios.de">Opensim-dev@lists.berlios.de</a><br> > >> </font></tt><a href="https://lists.berlios.de/mailman/listinfo/opensim-dev"><tt><font size="2">https://lists.berlios.de/mailman/listinfo/opensim-dev</font></tt></a><tt><font size="2"><br> > > <br> > > <br> > > <br> > > <br> > > ------------------------------------------------------------------------<br> > > <br> > > _______________________________________________<br> > > Opensim-dev mailing list<br> > > <a href="mailto:Opensim-dev@lists.berlios.de">Opensim-dev@lists.berlios.de</a><br> > > </font></tt><a href="https://lists.berlios.de/mailman/listinfo/opensim-dev"><tt><font size="2">https://lists.berlios.de/mailman/listinfo/opensim-dev</font></tt></a><tt><font size="2"><br> > _______________________________________________<br> > Opensim-dev mailing list<br> > <a href="mailto:Opensim-dev@lists.berlios.de">Opensim-dev@lists.berlios.de</a><br> > </font></tt><a href="https://lists.berlios.de/mailman/listinfo/opensim-dev"><tt><font size="2">https://lists.berlios.de/mailman/listinfo/opensim-dev</font></tt></a><tt><font size="2"><br> </font></tt>_______________________________________________<br>Opensim-dev mailing list<br><a href="mailto:Opensim-dev@lists.berlios.de">Opensim-dev@lists.berlios.de</a><br>https://lists.berlios.de/mailman/listinfo/opensim-dev<br></blockquote></div><br></div></div></div></body></html>