| Commit message (Collapse) | Author | Files | Lines |
|
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.
|
|
|
|
* Normalized m_inventoryService
* Pulled AddActiveGestures up
|
|
* Sometimes, null is a valid return value to indicate 'none found'. doh.
* Sometimes, the Grid server does not send simURI - this you need to reconstruct yourself. Euw.
(I believe) this solves mantis issue #3287
|
|
|
|
* Finally got to the point where I could pull up the CustomiseResponse function. Major de-duplication.
* Introduced FromRegionInfo on RegionProfileData
* This revision needs both grid and standalone testing galore.
Work in progress!
|
|
|
|
use (naming is a work in progress...)
* introduced new IRegionProfileService that is going to be _one_ profileService
* Had GridDBService inherit the IRegionProfileService
(preparing for re-wiring things and de-duplicating eventually)
|
|
|
|
"module".
Added OpenSim.Grid.UserServer.Modules project/dll which now contains the components of the userserver. With the OpenSim.Grid.UserServer being the setup and initiate exe.
|
|
|
|
being set, and that's what's being used in SendAppearanceToOtherAgent. Mantis #3204.
|
|
are now being given a default appearance if there is none in the user database. This issue affected newly created accounts, which aren't given an appearance at time of creation. May address some of the issues reported in mantis #3204 (but the incompatibility with pre-8447 is unaffected and continues to exist).
|
|
user service/server. Appearance is now sent by the user service/server along with all other loginparams. Regions don't query the user service for appearance anymore. The appearance is passed along from region to region as the avie moves around. And, as before, it's stored back with the user service as the client changes the avie's appearance. Child agents have default appearances that are set to the actual appearance when the avie moves to that region. (as before, child agents are invisible and non-physical).
|
|
reflect actual use.
* Added IRegionProfileService
|
|
|
|
|
|
|
|
identical to LocalLoginService.CustomiseResponse in order to be able to pull them up.
|
|
* fixes mantis #3092: User Server sets agent starting position to passed x/y/x instead of x/y/z
|
|
* This ensures that the user will be logged off successfully by a properly permissioned user server
|
|
* CapsUtil.GetRandomCapsObjectPath(); contains a / and the regionInfo.httpServerURI contains a / so that makes
* response.SeedCapability = regionInfo.httpServerURI + CapsUtil.GetCapsSeedPath(capsPath); contain two "//" leading to a seed caps path definition like //CAPS/f7ba4238-ec86-4a2b-b3f6-4d9b56070000/, which is wrong
|
|
|
|
terminology used elsewhere
* Last build break was probably a Bamboo failure - hopefully this should succeed
|
|
|
|
|
|
* Test does not do authentication
|
|
|
|
class. Thanks sdague for the protip!
|
|
|
|
|
|
justice.
|
|
|
|
Thank you, sacha magne, for a patch to add login level and message
commands to the user server
|
|
required to log in. set_login_params accepts avatar_uuid and password of a
user with god level 200 or more, and allows setting either or both the
login_motd or login_level
|
|
Active gestures are sent as part of the login-response. Added
fetchActiveGestures to SQLite and MySQL; added an empty one for MSSQL and
NHibernate. Using the empty ones won't cause errors, but doesn't provide
persistence either, of course.
|
|
* This patch aims to introduce look at direction persistence between logins. It won't be active until the second part of the patch is committed in about two weeks time. At
this point, region servers that haven't upgraded past this revision may run into problems
* This checkin upgrades the user database. As always, we recommend you have backups in case something goes wrong.
* Many thanks to tyre for this patch.
|
|
|
|
same as the original login region
|
|
* This may possibly (est. 20% change) help the situation that we see on OSGrid meetings when a region stops accepting logins, which appears to be because it never receives the expect_user request
|
|
* Now it should properly inform the user and stop a login if a region server could not be contacted in order to expect a user (the last commit didn't actually quite work correctly)
|
|
emergency region login code is a cut and paste job of the preceding normal region login code
* also, properly tell the user if no region can be contacted, rather than letting the login proceed only to fail later when authentication fails on the region side
* copying and pasting code... it makes me cry inside... so sad...
|
|
selected region fails, rather than swallowing it
|
|
process easier
* documentation
|
|
* This is a HUGE OMG update and will definitely have unknown side effects.. so this is really only for the strong hearted at this point. Regular people should let the dust settle.
* This has been tested to work with most basic functions. However.. make sure you back up 'everything' before using this. It's that big!
* Essentially we're back at square 1 in the testing phase.. so lets identify things that broke.
|
|
The attached patch (against r6075) fixes it for grid-mode. If the
home-region isn't available, the stored regionHandle will be used
to compute the region-coordinates of the home. This will be wrong
if the home-region has moved, of course, but without the region
being online we can't request the RegionInfo of it for finding out.
Doing that (before the patch) and accessing the (null) RegionInfo
led to a NullReferenceException, which prevented logging in to the
last location.
|
|
|
|
to make it easier to work with.
|
|
|
|
The attached patch fixes that your home-location icon is
displayed on the region you logged in, not on your home-region.
|