| Commit message (Collapse) | Author | Files | Lines |
|---|
|
* Implements 'Teleport Home'
* User Server has to be updated for it to save your home in grid mode
* home position accuracy is in int because the grid comms ExpectUser method tries to convert to Uint and crashes if it gets a float. Added a convert to decimal in ExpectUser but to avoid a breaking change with old revisions, kept the save value in int for now. Eventually it needs to be a float, but lets release another incremental version before doing that.
|
|
ar.AsyncWaitHandle.WaitOne(timeOut*1000, false); call.
|
|
avoid a potential race condition. As IAsyncResult.AsyncWaitHandle.WaitOne before a AsyncCallback is called. So in this case, its a race to see who sets or reads the bool m_bAvailable first.
|
|
when they were.
* A few things for testing.
* This makes a modification to the region registration with the grid server so that the region can send it a chosen password to identify itself. It will not cause any errors, if either one are not updated.
|
|
duplicate sets of inventory data to be sent over the grid
* Won't actually fix anything, since we were handling the problem anyway
* Also add more doc, fix up debugging messages, etc
|
|
|
|
before the region had completely received the inventory for the user.
* A much larger race condition where the inventory request could be made before the region gets any data at all will also be fixed in the near future.
* This change also fixes a regression from two patches ago where items stopped appearing in standalone inventory
|
|
|
|
at once, rather than each individual
* This is required in order to work towards eliminating some inventory race conditions and to better deal with situations where a grid inventory server is slow or not responding.
|
|
you when your friends come online if they're at least a child agent on the sim. offline status works the same also. So does Instant Message.
* This is until Grid Comms matures a bit more on this.
* This should also work in Standalone as it uses the IUserData interface.
|
|
|
|
|
|
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.
|
|
* wrap attributes in properties
* clean up names a little bit
* clean up name styles
|
|
|
|
create new inventory folders
* This mirrors the grid behaviour
|
|
* This update breaks inter-region communications, sorry.
* You will need to run prebuild.
Next, the good;
* This update solves the unexpected binary element when Linux simulators inform windows simulators and vice versa. So Linux Simulators and Windows simulators are 100% compatible again.
* This update introduces an Integer in the prim crossing method to tell the receiving simulator which XML method to use to load the prim that crossed the border. If the receiving prim doesn't support the method, the prim crossing fails and no prims are lost.
That being said, it's best to update all your simulators to this revision at once.
|
|
implemented anyway.
|
|
than just the root child folders
* This may resolve some current problems with non root child folders on standalone installations.
* A fix for the same problem in grid mode will come soon.
|
|
|
|
* Replace the unused default GetInventorySkeleton() impleemntation with an abstract declaration - less confusing this way imho
* Add some comments
|
|
|
|
(user server timeout)
* Increasing GetUserProfile requests only to 6 seconds from 3
* Not completely sure what effect this will have, though probably not much
* At some point one will have to accept that if the grid servers are taking many many seconds to respond, running using that grid will not be viable.
* Perhaps there should be a big warning up front if grid request times are slower than n seconds.
|
|
* Comments, capitalization
|
|
Some of these may be temporary
|
|
|
|
|
|
* Leaving quite a few debug messages in for now to help deal with bugs arising
|
|
|
|
response to osgrid issues)
* Not sure what the effect will be, but can't be any worse than the current constant sim crashes.
|
|
* 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
|
|
was trying to look up
|
|
SceneCommunicationService.EnableChildAgents so we can see what hostname is failing
|
|
n=5), we now drop the subsequent requests
* This may improve region memory usage
* This is a short-term response to a problem whereby some clients keep requesting the same texture even after we've sent it
* This treats the symptom rather than the cause.
* n can be adjusted by changing the constant at the top of UserTextureDownloadService if necessary
|
|
commented out) to find out what CAPS is doing
|
|
* Now the operation will just fail and post a message to the log instead, which may be mysterious to the client but isn't so brutal
|
|
|
|
|
|
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.
|
|
|
|
* Tell the log whether the sim is started in standalone or grid mode
|
|
|
|
* Indulge in my fetish for console message conformity
|
|
neighbouring region is down), put out only the source and message of the RemotingException (not the stack trace) to the console.
* It doesn't appear that the remoting stack trace yields any useful information anyway
|
|
from standalone services
|
