aboutsummaryrefslogtreecommitdiffstatshomepage
path: root/OpenSim/Framework/Communications/Cache/CryptoGridAssetClient.cs (follow)
Commit message (Collapse)AuthorAgeFilesLines
* Minor: Change OpenSim to OpenSimulator in older copyright headers and ↵Jeff Ames2009-06-011-1/+1
| | | | LICENSE.txt.
* Intermediate commit. WILL NOT COMPILE!Melanie Thielker2009-05-041-1/+1
|
* * Explicitly start the asset server thread so that unit tests can run single ↵Justin Clarke Casey2009-04-141-5/+0
| | | | rather than multi-threaded (which may be behind the occasional test freezes)
* - remove the Metadata property from AssetBase and return all previousMike Mazur2009-02-171-9/+9
| | | | | | | | | properties as before - prefix private variables with m_ in AssetBase.cs - related to Mantis #3122, as mentioned in https://lists.berlios.de/pipermail/opensim-dev/2009-February/005088.html - all services will likely need to be upgraded after this commit
* From: Alan Webb <awebb@linux.vnet.ibm.com>Sean Dague2009-02-161-8/+40
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The change makes two principal implementation changes: [1] It removes the hard coded set of possible asset server client implementations, allowing any arbitrary implementation that has been identified to the PluginLoader as an appropriate extension. The extension point for asset server client extension is /OpenSim/AssetServerClient. All of the old configuration rules have been preserved, and any of the legacy configuration values will still work as they did before, except the implementation is now loaded as a plug-in, rather than as a hard-coded instantiation of a specific class. The re-hashing of IAssetServer as an extension of IPlugin made upgrading of the implementation classes a necessity. Caveat: I have not been able to meaningfully test the crypto-grid clients. I believe they should work correctly, but the refactoring necessary to handle plug-in based initialization (vs constructor-based initialisation) admits the possibility of a problem. [2] The asset cache implementation, previously introduce as a hard-code class instantiation is now implemented as an IPlugin. Once again the previous (configurationless) behavior has been preserved. But now it is possible for those interested in experimenting with cache technologies to do so simply by introducing a new extension for the asset cache extension point (/OpenSim/AssetCache). I've tested all of the configuration settings, after applying the patch to a newly extracted tree, and they seem to work OK.
* * optimized usings.lbsa712009-02-121-2/+2
|
* This changeset is the step 1 of 2 in refactoringDr Scofield2009-02-061-2/+8
| | | | | | | | | | | | | | | | | | | | OpenSim.Region.Environment into a "framework" part and a modules only part. This first changeset refactors OpenSim.Region.Environment.Scenes, OpenSim.Region.Environment.Interfaces, and OpenSim.Region.Interfaces into OpenSim.Region.Framework.{Interfaces,Scenes} leaving only region modules in OpenSim.Region.Environment. The next step will be to move region modules up from OpenSim.Region.Environment.Modules to OpenSim.Region.CoreModules and then sort out which modules are really core modules and which should move out to forge. I've been very careful to NOT BREAK anything. i hope i've succeeded. as this is the work of a whole week i hope i managed to keep track with the applied patches of the last week --- could any of you that did check in stuff have a look at whether it survived? thx!
* - add OpenSim.Framework.AssetMetadata class. AssetBase is now composed of itMike Mazur2009-02-041-23/+23
| | | | | - trim trailing whitespace
* killing warnings, reformatting RemoteAdminPluginDr Scofield2008-12-051-5/+4
|
* fix line endings, as apparently the bot didn't do this yetSean Dague2008-10-161-527/+527
|
* * Adding CrytoGridAssetClient support - allows encrypting assets that are ↵Adam Frisby2008-10-141-0/+527
stored on a potentially hostile grid. This is not DRM, not should be relied on until after it's been security audited. I'll write a blog post on this explaining how/why/when you should use this, and what it does.