| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
| |
* Looks like these weren't so unused after all - oops!
* Remove message from grid server config
|
|
|
|
| |
GetInventorySkeleton
|
|
|
|
| |
the specific inter service class
|
|
|
|
|
|
| |
And reverted CachedUserInfo back to revision 5262.
I don't think most of the inventory problems that people are reporting are due to these, but its easier to deal with one set of potential problems at a time, and I'm not going to get any time in the week to work on this anyway.
|
|
|
|
| |
in the loginservice
|
|
|
|
| |
time to look into the problems people are having.
|
| |
|
|
|
|
|
|
|
|
|
|
| |
The Login service should now read/create new inventory on the inventory server that is set in a users profile.
Also added "Add-InventoryHost" console command to add a support for a new server to a region.
So it would be good if someone could test this. Set up the grid as normal, but then also run extra inventory server on a different computer (well actually it just has to be on a different network hostname, so one using "http://localhost:8004" and one using "http://127.0.0.1:8005" should work) then you need to manually edit the user profile database to set the new servers url in a user's "userInventoryURI" field.
Then on a region server, use the Add-InventoryHost to add the new server url (always include the full url, including http, but don't add a final /)
Login with that account and see if the inventory works.
Of course these needs to be made more user friendly.
|
|
|
|
|
|
|
|
| |
World->Region/Estate. Then on the Estate tab, at the lower right hand corner, clicking the 'Add' button and picking an avatar.
* It only persists across reboots for the mySQL datastore currently.
* Currently have stubs in the other datastores.
|
|
|
|
|
|
|
| |
* User tries to log-in but is already logged in. Userserver will send message to simulator user was in to log the user out there.
* From the UserServer, admin types 'logoff-user firstname lastname message'.
* Some regions may not get the message because they're not updated yet.
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
with namespaces.
|
|
|
|
| |
(this took a while to run).
|
|
|
|
| |
skeleton has been successfully created.
|
|
|
|
|
|
|
|
| |
console from sync to async
* Catch more error conditions and provide more messages when things go wrong
|
|
|
|
|
|
|
|
| |
than async.
* Add more error checking so that we don't proceed if there has been a problem with inventory retrieval
|
|
|
|
|
|
|
|
| |
empty response to a whole agent inventory request, then post an inventory login failure message.
IMO, this is better than allowing the agent to login with an apparantly blank inventory.
|
| |
|
|
|
|
| |
up log messages
|
|
|
|
| |
if a login fails because the inventory service has failed.
|
| |
|
|
|
|
|
|
|
| |
grief than expected, as monodevelop doesn't like to refactor
properties of properties.
|
| |
|
|
|
|
|
|
|
| |
actually a little more work than I expected given the copious
use of out params.
|
|
|
|
|
| |
Thanks lulurun!
|
|
|
|
|
|
|
|
| |
* wrap attributes in properties
* clean up names a little bit
* clean up name styles
|
| |
|
|
|
|
|
|
|
|
| |
create new inventory folders
* This mirrors the grid behaviour
|
|
|
|
|
|
|
|
|
|
|
|
| |
affect once the region and the grid servers have upgraded to this revision
* You may also need to clear your cache before seeing any effect.
* These fixes may or may not affect inventory on the RC client.
* These fixes should make non-root folders work better, stop inventory failure on first login, allow trash to be emptied and make texture picker in object edit view work properly
* Fixes are 1) make initial root folder request wait for async inventory delivery, 2) deliver all folders in the initial login skeleton, not just the root child ones and 3) deal
with situations where we receive child folders from the inventory service before their parent is received.
|
|
|
|
|
|
|
| |
* Replace the unused default GetInventorySkeleton() impleemntation with an abstract declaration - less confusing this way imho
* Add some comments
|
| |
|
|
|
|
|
|
| |
* Leaving quite a few debug messages in for now to help deal with bugs arising
|
|
|
|
|
|
|
|
|
|
|
| |
* This means that caps methods (editing scripts, poss map functions, etc) on non-home regions should now work with servers which are listening for http ports on a non default
(9000) port.
* If you are running a region server, this may only work properly once your grid server upgrades to this revision
* PLEASE NOTE: This shouldn't cause inter-region problems if one end of the connection hasn't upgraded to this revision. However if it does, the instability will persist until
the grid and region (and possibly all the region's neighbours) have upgraded to this revision.
* This revision also adds extra login related messages, both for success and failure conditions
|
| |
|
|
|
|
|
|
|
| |
location box and go to that region if it's there. If no close match was found, it sends you home. This is tested on mySQL. There's untested code on grids that are based on sqlite and MSSQL. The SQL statements *should* be right, but your results may very.
* Ex, if you want to go to Wright Plaza, you simply need to type Wright Plaza in the start location in the client when you log-in.
|
| |
|
| |
|
|
|
|
|
| |
* Server now listens to the client's start location request for 'home' or 'last' and sends the user to the home location or the last location.
|
|
|
|
| |
support for region move/split/merge. See ThirdParty/3Di/README.txt. Unless the new modules are used there should be no noticeable changes when running OpenSim.
|
|
|
|
|
|
|
|
| |
appropriate names consisten with their use.
All done with all 94 handlers from handler001
through handler094. Hopefully we can move
forward without numbered handlers.
|
| |
|
| |
|
|
|
|
| |
instances to prevent event race conditions
|
| |
|
|
|
|
|
|
|
|
|
| |
region server on login
* This will make it more obvious if one accidentally starts one's region server in standalone rather than grid mode but then tries to login to a grid (as I am wont to do)
* We are now sending back a fault code (-32601) if no xmlrpc method is found rather than an ordinary message
|
|
|
|
|
|
| |
* Minor documentation bits
|