| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
FindFolder()
|
|
|
|
| |
won't be useful until we let the client cache (again?)
|
| |
|
|
|
|
| |
prefixes
|
|
|
|
| |
arguably should be split)
|
| |
|
|
|
|
| |
exists when in fact it does not
|
|
|
|
|
|
|
|
| |
CachedUserInfo
* Remove unused/superseded methods from GridInventoryService
|
|
|
|
|
|
| |
* Put warning in remove folder method about non implementation (not that this is used anyway - may be legacy)
|
|
|
|
|
|
| |
* Remove old framework asset transactions files which were region modularized
|
| |
|
|
|
|
|
|
|
|
| |
almost every inventory method
* This allows lots of redundant inventory methods with only slightly different names to be eliminated.
|
| |
|
|
|
|
|
| |
* Made a bunch more members static, removed some dead code, general cleaning.
|
| |
|
| |
|
|
|
|
|
|
|
| |
* The resolution takes the form of not crashing the session if the folder the user is attempting to add already exists (e.g. there is one already with the same UUID).
* Printing out warnings instead
|
|
|
|
| |
one log message changed)
|
|
|
|
|
|
|
| |
Thanks A_Biondi and Melanie!
* This builds but might not work. JustinCC will examine.. it may work out of the box.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
and detach from inventory.
* Detaching from right clicking in world, detaches to your inventory.
* If you go up to a prim and attach it from in world, it appears in your inventory.
* Attachment placement is saved when you detach them.
* Choosing wear remembers your last attachment point from inventory.
* Wrote a method to update an inventory item's asset and sends the updated inventory item to the Client
* Wrote a recursive method to find the folder of a known existing inventory item.
* Removed a block on physics object position on creation. This might crash a region or two, let us know via Mantis if your region crashes because of a physics out of bounds error.
* Drop doesn't work. The menu item doesn't even come up. Don't know why :P.
|
|
|
|
|
|
|
|
|
|
| |
inventory
* Now, if you own an item in a prim, you should be able to successfully drag it back into your inventory
* Temporarily, users which are not owners of the item cannot copy it, even if 'everyone can copy' is set
* This is pending fixes/implementation of upstream permission implementation
|
|
|
|
|
|
|
|
|
| |
* Now, emptying the trash should remove folders and the items they contain as well as items which were not in a subfolder.
* This will only work once both the region and grid servers have reached this revision.
* You may also need to clear your cache before this will work
* Refactoring to follow.
|
|
|
|
|
|
|
|
| |
this will work for sqlite and nhibernate, but will be ignored for
mysql and mssql (reverting to their ini files) until someone writes
that bit.
|
|
|
|
|
|
|
| |
* On standalone, folders (and their items) should now be persistently deleted on trash emptying, as well as immediate child items
* An implementation for grid mode will follow.
|
|
|
|
| |
places other than directly under "My Inventory" should now be stored
|
|
|
|
|
|
|
|
| |
InventoryFolderImpl carried out by CachedUserInfo
* These will do temporarily pending refactoring
|
|
|
|
|
|
|
|
| |
will be soon
* Add locking to InventoryFolderImpl class - need more though.
|
|
|
|
|
|
|
|
| |
to create folder, move folder and purge folder.
* Old 1.18 get folder functionality requires a little more consideration
|
| |
|
|
|
|
|
|
|
|
|
| |
received by a region from the inventory service
* This replaces the old behaviour of failing straight away, which could cause lost updates if the inventory service was slow in responding
* This is the first baby step to making all inventory requests behave this way, to reduce inventory lossage
|
|
|
|
| |
(this took a while to run).
|
|
|
|
|
|
|
| |
* A much more significant fix is required to clean up the cache when a user moves out of a region, but really better handling of delayed inventory cache updates needs to be
written first, and possibly better affinity to cut down agent inventory requests when the move is between two regions hosted on the same server.
|
|
|
|
| |
first point of call rather than the grid owner
|
|
|
|
|
| |
* This fixes chi11ken's/OpenViewer's libsl cap issue.
|
|
|
|
|
|
|
|
|
|
| |
fixed path
* This allows caps requests to be routed to regions where the agent is currently a root agent instead of the region that they logged into as it did previously.
* This fixes a wide variety of bugs related to 'can't do X once i've crossed a border'.
* The first seed cap request fails, the second one works. (this generates an error message on the console)
* Experimental.
|
|
|
|
|
|
|
|
|
| |
rather than simply returning 0 items.
* This is very early support which would only be triggered in a rather unlikely case (if the user server correctly received an inventory skeleton, but later on failed to return the whole inventory in a timely manner. Also, this only applies to the 1.19.1.4 client onwards
* Code cleanup and support for other failure cases (failure of inventory caching on region crossing, failure to actually add a folder/item, etc, should follow.
|
|
|
|
|
|
|
|
|
| |
delivery from the inventory service
* This will reduce failures where the inventory server is simply slow
* Still need to properly inform the user if the inventory service has failed altogether
|
| |
|
|
|
|
|
|
|
|
|
| |
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.
|
|
|
|
| |
more readable, and make RootFolder get only
|
| |
|
| |
|
| |
|
|
|
|
| |
Preparation for handling inventory problems where the inventory server receives a request and never responds, or is late in responding
|
| |
|
|
|
|
|
|
|
| |
actually a little more work than I expected given the copious
use of out params.
|
|
|
|
|
|
| |
to reflect what they really are.
|
|
|
|
| |
what just went wrong
|