opensim-SC_OLD - My fork of OpenSim for IG and MG, called SledjChisl.

	Commit message (Collapse)	Author	Files	Lines
2009-04-14	Adds session authentication upon NewUserConnections. Adds user key ↵	diva	1	-5/+5
	authentication (in safemode only) upon CreateChildAgents. All of this for Hypergrid users too. This addresses assorted spoofing vulnerabilities.
2009-03-29	Another bit of refactoring to try to make sense of ↵	diva	1	-1/+2
	OpenSim.Framework.Communications. Everything that looks like a service, with service handlers, moved to .Services -- i.e. LoginService and Response, and GridInfoService. The rest of the changes were to adapt to the new locations of those files.
2009-03-20	* De-duplicated login service some more	lbsa71	1	-19/+0
	* Normalized m_inventoryService * Pulled AddActiveGestures up
2009-03-10	* Cleanup and CCC (Code Convention Conformance)	lbsa71	1	-21/+21

2009-03-06	Added a output message to CreateCommsManagerPlugin for when a user tries to ↵	MW	1	-36/+46
	run with both -hypergrid=true and -background=true command line arguments. As these two don't work together as they initialise different root OpenSim classes. I was going to change it back to the old behaviour where in that usecase it would just startup in the background but without hyerpgrid enabled. But think its better to give a error about this and then exit, so the user knows to change their settings. Rather than later wondering why hypergrid isn't working.
2009-03-03	Moved Linden protocol login handling to modules in OpenSim.Client.Linden. ↵	MW	1	-17/+16
	There are two region modules in there LLStandaloneLoginModule (for standalone mode) and LLProxyLoginModule (for grid mode which just handles incoming expect_user and logoff_user messages from the remote login server) Changed OpenSim.Framework.Communications.Tests.LoginServiceTests to use the LLStandaloneLoginService (from the LLStandaloneLoginModule) rather than LocalLoginService. Really these login tests should most likely be somewhere else as they are testing specific implementations of login services. Commented out the old LocalLoginService as its no longer used, but want to check there are no problems before it gets deleted.
2009-03-03	Refactoring of CreateCommsManagerPlugin.	MW	1	-32/+28
	Plus some general cleanup of a few other files (deleting excess blank lines etc)
2009-03-02	Added more error info to CreateCommsManagerPlugin.	MW	1	-0/+1

2009-03-02	Added some debug output to CreateCommsManagerPlugin	MW	1	-1/+11

2009-02-27	Changed the CreateCommsManagerPlugin so it requests a IRegionCreator and ↵	MW	1	-4/+3
	subscribes to the OnNewRegionCreated event on that interface rather than requesting the LoadRegionsPlugin directly. Removed the reference to OpenSim.ApplicationPlugins.LoadRegions from the CreateCommsManagerPlugin project.
2009-02-26	svn attribute fixes so that we can play nice between windows and linux	Sean Dague	2	-267/+267

2009-02-26	Added IRegionCreator interface that all ApplicationPlugins that are creators ↵	MW	1	-0/+1
	of Scenes should implement and register with the ApplicationRegistry.StackModuleInterface<>(); So that other plugins can attach to their OnNewRegionCreated event. Made some changes to IRegistryCore and RegistryCore so they support "Stacked" interfaces.
2009-02-26	Another change to how the CreateCommsManagerPlugin checks if it should be ↵	MW	1	-1/+2
	creating HG or normal CommunicationsManager.
2009-02-26	Changed CreateCommsManagerPlugin so it handles external subclasses of ↵	MW	1	-9/+10
	OpenSimBase. This process of checking if it should be creating HG or normal CommunicationsManager needs to change. So look out for a revert of this whole plugin soon.
2009-02-26	Moved the Initialisation of the CommunicationsManager to a ApplicationPlugin.	MW	2	-0/+264
	Also in that plugin it registers the IUserService with all the Scenes (as they are created). So now we can start changing over all uses of IUserService, that currently access it from the CommunicationsManager to accessing it from the Scene.RequestModuleInterface call. Once that is done we can move the UserService creation out to its own plugin and remove all references to it from the CommunicationsManager. Then we can take the next CommunicationsManager interface and repeat.