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