| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
default under [Startup]. They can then be overwritten in the other sections (but probably shouldn't). I kept the existing code for backwards compatibility, so this should not cause any breaks from people's current configurations. But people should move to have these 2 vars under [Startup] -- see OpenSim.ini.example and Robust.HG.ini.example. And yes, both names now end with "URI" for consistency.
|
| |
|
|
|
|
|
|
|
|
| |
This is mostly Bluewall's work but I am also bumping the general version number
OpenSimulator 0.7.5 remains in the release candidate stage.
I'm doing this because master is significantly adding things that will not be in 0.7.5
This update should not cause issues with existing external binary DLLs because our DLLs do not have strong names
and so the exact version match requirement is not in force.
|
|
|
|
| |
went wrong, rather than a possibly unhelpful simple exception message.
|
| |
|
| |
|
|
|
|
| |
We do this in OpenSim.exe to hide output when unmanaged dll are scanned by mono addins. Libomv has hard-coded path to "." for the openjpeg libraries, causing output to the console when they are scanned. We will cover this up for now, then look at getting libomv to look for the libs outside the "." later.
|
|
|
|
| |
Had moved the class to a different namespace but failed to add the reference
|
|\
| |
| |
| |
| | |
Conflicts:
OpenSim/Server/Base/ServicesServerBase.cs
|
| |
| |
| |
| | |
This also allows comments in command scripts (lines starting with ;, # or //) to be used across all servers
|
| | |
|
| |
| |
| |
| | |
Log path at which pid file is created or reason for failure to create.
|
| | |
|
| |
| |
| |
| | |
This helpfully lists version information, startup location and console log level
|
| | |
|
| | |
|
| | |
|
| |
| |
| |
| | |
Request) HTTP status rather than simply dropping the request.
|
| |
| |
| |
| | |
Adds new OpenSim.Server.Handlers.Tests.dll to test suite
|
| | |
|
| | |
|
| |
| |
| |
| |
| |
| | |
This allows a closed grid to delete asset types other than maptile remotely.
Only operational if AllowRemoteDelete = true also.
Defaults to false - do not enable if anybody other than you can make asset service requests.
|
| |
| |
| |
| |
| |
| |
| |
| | |
from AssetService.
This allows us to use a common check for both AssetService and XAssetService.
It also allows future console commands to delete an asset.
As before, deletion of maptile assets is not allowed remotely unless this is explicitly configured.
|
| |
| |
| |
| |
| |
| | |
filename to save already exists, rather than exception throwing.
Also changes ConsoleUtil.CheckFileExists to CheckFileDoesNotExist() since this is more meaningful in the context, even though it does result in double negatives.
|
| |
| |
| |
| | |
Move PluginManager out to OpenSimFramework for general use
|
| | |
|
| |
| |
| |
| | |
Plugin may be enabled and disabled on the fly.
|
| |
| |
| |
| | |
Rebuild registry if loading from a local dll to give access to the addin data for it on the first pass.
|
| | |
|
|\ \
| |/
| |
| |
| | |
Conflicts:
OpenSim/Server/ServerMain.cs
|
| | |
|
| | |
|
| | |
|
| |
| |
| |
| | |
This is working - more testing to follow, then soem documentation
|
|/
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
We can provide modular ini for connectors...
look for our configuration in the following places...
1) in the default ini/-inifile
2) in the named file (ConfigName) located in the configured directory
(see Robust[.HG].ini [Start] section for ConfigDirectory)
3) in the repository named in the connector (ConfigURL)
In this case, the file will be written into the configured
directory with the specified
See example connector/service @ https://github.com/BlueWall/SlipStream
for testing.
|
|
|
|
|
|
| |
(present as column PrincipalID) parameters in the Avatars table.
These are used to invoke avatar service calls but are not in themselves persistable avatar data.
|
|
|
|
| |
Signed-off-by: BlueWall <jamesh@bluewallgroup.com>
|
|
|
|
|
|
| |
the BOM, use a single Util.UTF8NoBomEncoding.
This class is thread-safe (as evidenced by the provision of the system-wide Encoding.UTF8 which does not suppress BOM on output).
|
|
|
|
|
|
|
| |
constructing fresh copies.
The encodings are thread-safe and already used in such a manner in other places.
This isn't done where Byte Order Mark output is suppressed, since Encoding.UTF8 is constructed to output the BOM.
|
| |
|
|
|
|
|
| |
It appears this was never actually used since attachments were rezzed in other code.
This was never available on remote simulator comms, only local.
|
|
|
|
|
|
| |
This allows one to see incoming requests as they happen.
This required making everything use the common MainServer class for registering and retrieving http servers, rather than duplicate structures.
|
|
|
|
|
|
| |
logic.
This does require the server to be added before it is set as the main Instance
|
|
|
|
|
|
|
|
|
|
| |
of always true no matter what the callee actually returned.
This was due to two things
1) SimulationServiceConnector.QueryAccess was always looking to the outer result["success"].
But if a "_Result" map is returned (which is certainly the case right now), then the true success is _Result["success"], result["success"] is always true no matter what
2) If QueryAccess was false at the destination, then AgentHandlers.DoQueryAccess() was never putting this in the result.
The default action of SerializeJsonString() is not to put false booleans in the JSON!!!, so this has to be explicitly set.
|
|
|
|
| |
lookup rather than the region handle.
|
|
|
|
|
|
|
|
|
|
| |
ServerUtils.BuildXmlData() and ParseElement()
If AvatarService appearance data is retrieved over the network, then ServerUtils was attempting to transfer names such as "Wearable 0:0" directly to xml element names, resulting in an exception.
Space is not valid in xml element names. Neither is : in this case since the intention is not to namespace. Using names directly as keys is not a good idea.
To get around this problem this patch escapes and unescapes the element names as appropriate.
This has no impact on existing xml (since it had to be valid in the first place) but allows AvatarService data to be used over the network.
Setting appearance (from simulator to AvatarService) did not suffer this problem since the values are passed in the query string which is already properly escaped.
|
|
|
|
|
|
| |
requests, as this appeared to be some kind of numbered error code.
This brings these messages into line with similar messages that did not do this.
|
|
|
|
|
|
| |
can relate a slow request to what the handler actually does and the agent it serves, if applicable.
This is most useful for capabilities where the url is not self-describing.
|
|
|
|
| |
because they were being uploaded before the region was registered with the grid
|
| |
|