Diva,

 

actually, I don't know how far away we are.

 

The problem is that somewhere way back when, there was a lot of copy+pasteing 
"to get things to work"(tm) - which led to the login services being textually 
almost identical, but perusing different classes. (IE, local Uses RegionInfo to 
work with region settings, grid uses RegionProfileData) - classes taht we are 
wary of working with because they are potentially serialized.

 

My focus right now, today even, is to try and pry the RegionInfo out of 
RegionProfiles cold dead hands. I thought I succeeded, but alas, more debugging 
seems to be needed.

 

Once I (or we, by all means) have gotten to the point where I (we) have 
de-duplicated the backend services, modularizing them should not be that hard. 
(knock on wood)

Best regards,
Stefan Andersson
Tribal Media AB



 
> Date: Wed, 11 Mar 2009 19:05:05 -0700
> From: [email protected]
> To: [email protected]
> Subject: Re: [Opensim-dev] More login refactoring
> 
> Actually, it's more than modules pertaining to the User Services. The 
> Grid Services too. Specifically, these two
> 
> m_httpServer.AddXmlRPCHandler("map_block", 
> XmlRpcMapBlockMethod);
> m_httpServer.AddXmlRPCHandler("search_for_region_by_name", 
> XmlRpcSearchForRegionMethod);
> 
> Standalones may also want to provide these services, especially with 
> better clients coming on the horizon.
> 
> The Hypergrid already has some of those modules for standalones, namely 
> Inventory and Asset, so that inventory of standalone users can be 
> accessed from the outside. But, really, this is not the right way of 
> doing it, because it has a fair amount of code duplication with what's 
> in the corresponding Servers.
> 
> Any ideas?
> And apologies if this touches again on the heated discussion between MW 
> and Melanie a couple of weeks ago...
> 
> 
> Diva Canto wrote:
> > Lbsa/MW,
> >
> > I know you have been refactoring the login code a bit. I wonder if 
> > you're stopping here or if there's more coming. The reason I ask is this.
> >
> > OpenSim.Framework.Communications.LoginResponse is pretty much the Linden 
> > Viewer login response, so it should go somewhere under Linden.Login. You 
> > already did part of this for standalone. But this brings up a bigger 
> > issue: substantial parts of the login code, including this LoginResponse 
> > but not only, are shared between Region (standalone) and 
> > Grid.UserServer. I wonder if there's a way of making them be modules 
> > that both the region server (in standalone mode) and the User server can 
> > load?
> >
> > Ideally, one would have a collection of Login modules that people can 
> > choose to support on their grids/standalones.
> >
> > How far are we from being able to do that?
> >
> > Crista
> > _______________________________________________
> > Opensim-dev mailing list
> > [email protected]
> > https://lists.berlios.de/mailman/listinfo/opensim-dev
> >
> > 
> 
> _______________________________________________
> Opensim-dev mailing list
> [email protected]
> https://lists.berlios.de/mailman/listinfo/opensim-dev
_______________________________________________
Opensim-dev mailing list
[email protected]
https://lists.berlios.de/mailman/listinfo/opensim-dev

Reply via email to