| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
command
|
|
|
|
|
|
|
|
|
|
| |
.NET 4.0 added the method Stream.CopyTo(stream, bufferSize). For .NET 3.5
and before, WebUtil defined an extension method for Stream with the signature
Stream.CopyTo(stream, maxBytesToCopy). The meaning of the second parameter
is different in the two forms and depending on which compiler and/or
runtime you use, you could get one form or the other. Crashes ensue.
This change renames the WebUtil stream copy method to something that
cannot be confused with the new CopyTo method defined in .NET 4.0.
|
|
|
|
| |
capitalization of 'name' to lower case, also in the same <grid> section.
|
| |
|
|\ |
|
| |
| |
| |
| |
| |
| | |
thread.
This was previous behaviour anyway.
|
| |
| |
| |
| | |
saying afterwards that we added it.
|
| |
| |
| |
| | |
rather than what they've just done.
|
| |
| |
| |
| |
| |
| |
| | |
at the asset service at once.
This may (or may not) improve reliability for http://opensimulator.org/mantis/view.php?id=5898
Quick tests show that save time is the same.
|
| |
| |
| |
| |
| |
| |
| |
| | |
This is configured in the new [Estates] section of OpenSim.ini.
If a default estate is configured then all new regions are automatically joined to it instead of asking the user.
If the default estate does not already exist then it is created.
Current default behaviour remains the same - the user is asked for estate details when necessary.
Thanks to Frenando Oliveira for the patch which I adapated further.
|
| |
| |
| |
| |
| |
| | |
makes use of the SLUtil copy via a method rather than each LLClientView loading a separate copy.
As per opensim-users mailing list discussion.
|
| |\ |
|
| | | |
|
| |/
|/|
| |
| | |
the PostToService variants.
|
| |
| |
| |
| |
| |
| | |
- Added an inventory cache for caching root and system folders
- Synchronized the remote inventory connector, so that all the remote inventory calls are serialized
This will not make much difference in the hold ups. We'd have to move the FireAndForget high up to AddInventoryItem, but that opens up a can of worms regarding the notification of the recipient... the recipient would be notified of the offer before the items are effectively in his inventory, which could lead to surprises.
|
| | |
|
|\ \
| |/ |
|
| |
| |
| |
| | |
This is rather than checking whether the avatar is sitting and doing its own calculation.
|
| |
| |
| |
| | |
this is handled by the necessary ParentPart check
|
| |
| |
| |
| |
| |
| |
| | |
(saving extra null checks, etc.)
However, it looks like we should retain SP.ParentID since it's much easier to use that in places where another thread could change ParentPart to null.
Otherwise one has to clumsily put ParentPart in a reference, etc. to avoid a race.
|
| |
| |
| |
| | |
(part != null), rather than having unnecessary multiple checks
|
|/
|
|
| |
functional asset posts so that the client threads doesn't freeze (but the network posts are serialized).
|
|\ |
|
| |
| |
| |
| |
| |
| | |
ParentPart is still not null if the ParentID != 0
Another thread could come in and stand the avatar between those two instructions.
|
| | |
|
| |\ |
|
| |\ \ |
|
| | | | |
|
| | | |
| | | |
| | | |
| | | |
| | | | |
This should not currently be used in any circumstances except for experimentation.
Database tables used by this plugin can still change at any time with no migration path.
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Some successful collision attacks have been carried out on sha1 with speculation that more are possible.
http://en.wikipedia.org/wiki/Cryptographic_hash_function#Cryptographic_hash_algorithms
No successful attacks have been shown on sha256, which makes it less likely that anybody will be able to engineer an asset hash collision in the future.
Tradeoff is more storage required for hashes, and more cpu to hash, though this is neglible compared to db operations and network access.
|
| | | | |
|
| | | |
| | | |
| | | |
| | | | |
configurable from outside MySQLXAssetData.
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Whether this is worthwhile is debatable since here we are not transmitting data over a network
In addition, jpeg2000 (the biggest data hog) is already a compressed image format.
May not remain.
|
| | | | |
|
| | | | |
|
| | |\ \ |
|
| | | | | |
|
| | |\ \ \ |
|
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
This is an extremely crude implemenation which almost works by accident. Nevertheless it does work.
It can be tested with the instructions at http://opensimulator.org/wiki/Feature_Proposals/Deduplicating_Asset_Service#Testing
It does not interact at all with the existing asset service or any data stored there.
This code is subject to change without notice and should not be used for anything other than gawking.
|
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
This is the start of exploring the creation of a bundled OpenSimulator asset service that does de-duplication and possibly file storage of assets.
Along the lines of coyled's SRAS, but not intended to replace, merely to act as a more performant bundled default.
Might end up nicking stuff from kcozen's patch at http://opensimulator.org/mantis/view.php?id=5429
More details at http://opensimulator.org/wiki/Feature_Proposals/Deduplicating_Asset_Service
Feedback and discussion welcome as commits are made.
|
| |_|_|_|/
|/| | | |
| | | | |
| | | | | |
pattern as suggested in the patch mantis #5921. Testing it in this smaller context to see how it works.
|
| | | | | |
|
|/ / / /
| | | |
| | | |
| | | | |
the check for significant is carried out. Prevents a deadlock condition.
|
| | | | |
|
| | | | |
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
are still lowercase.
Also convert the estate commands to simply AddCommand() calls so that commands from two different modules can be placed in the same category
|
|\ \ \ \ |
|
| |\ \ \ \ |
|
| | | | | | |
|
| |/ / / /
|/| | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
<category/module>" to display commands in a category.
This is to deal with the hundred lines of command splurge when one previously typed "help"
Modelled somewhat on the mysql console
One can still type help <command> to get per command help at any point.
Categories capitalized to avoid conflict with the all-lowercase commands (except for commander system, as of yet).
Does not affect command parsing or any other aspects of the console apart from the help system.
Backwards compatible with existing modules.
|