| Commit message (Collapse) | Author | Files | Lines |
|---|
|
handled by the base http server
|
|
* 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.
|
|
|
|
up log messages
|
|
if a login fails because the inventory service has failed.
|
|
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
|
|
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.
|
|
:: Believe it or not, but INSERT/UPDATE is actually a better pattern than REPLACE, since, with INSERT/UPDATE you can catch erroneous UPDATES to non-INSERTed items as well as catch erroneous re-INSERTS. in 95% of the cases, you SHOULD have a clear INSERT context, and a clear and separate UPDATE context. If you think your case falls within the 5%, maybe you should re-evaluate your code. ::
|
|
Preparation for handling inventory problems where the inventory server receives a request and never responds, or is late in responding
|
|
|
|
|
|
|
|
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!
|
|
to reflect what they really are.
|
|
* wrap attributes in properties
* clean up names a little bit
* clean up name styles
|
|
* wrap fields as Properties
* rename some fields/properties to more sensible names
* set style to PropName to match more standard C# approach
|
|
|
|
|
|
terrain as default seems better than the messed up terrain I was getting.
|
|
needs to be updated still.
* Adding some XMPP stuff that's incomplete.
|
|
adding a new inventory instead
|
|
create new inventory folders
* This mirrors the grid behaviour
|
|
* This change will have no functional impact - we were already filtering out the dupes on the other end.
|
|
implemented anyway.
|
|
what it used to do (not that the name was actually accurate in the first place)
|
|
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
|
|
|
|
* Comments, capitalization
|
|
* 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
|
|
an "Exception e" with e.ToString() to eliminate 2 warnings.
|
|
|
|
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.
|
|
|
|
Here's a diff of the changes I have made in support of the following LSL
script functions.
llSetScriptState
llGetScriptState
llCSV2List
llListRandomize
llList2ListStrided
llListFindList
llResetOtherScript
llGetScriptName
It was necessary to modify ExecutorBase in support of the ScriptState
implementations.
I also modified SceneObjectPart and SceneObjectPart.Inventory to
corrects a quoting mismatch in the commentary that through off live
parsing of the files.
I also simplified the State definition at the start of BuiltinCommands.
|
|
|
