| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| ... | |
| |
|
|
|
|
| |
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
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
grids like it.
|
| |
|
|
| |
Eliminated an extra newline in the console if the log line doesn't contain a category (example of a category: "[ASSETS]").
|
| | |
|
| |
|
|
| |
(XInventory and Assets).
|
| | |
|
| |
|
|
| |
owned by the same user.
|
| |
|
|
| |
that they can scale better. They were previously being handled by the UAS; that is still there, but it's now obsolete and will be removed in a future release.
|
| | |
|
| |
|
|
| |
co-presence in the same sim. Using avatar picker, users can now search for names such as "first.last@grid.com:9000", find them, and request friendship. Friendship requests are stored if target user is offline. TESTED ON STANDALONE ONLY.
|
| |
|
|
| |
direct user connections.
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
| |
<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.
|
| | |
|
| |
|
|
|
|
| |
potential bad update that places an object at the opposite side of the
origin sim for a moment before actually crossing it. Especially important in
grids like OSG where lag between sims is high.
|
| |
|
|
| |
queries fail.
|
| |
|
|
| |
config sections or files a bit more user friendly.
|
| | |
|
| |
|
|
| |
Make SRV_HomeURI available on the GridInfoService through the "/json_grid_info" URI. This i s mainly to service OSSL, but can be seen externally via the URI.
|
| |\ |
|
| | | |
|
| |/ |
|
| |
|
|
|
|
| |
service command be "show asset" instead of "show digest" this time.
Last time I accidnetally just changed the usage message.
|
| | |
|
| | |
|
| |
|
|
|
|
| |
harmonise the same commands on the simulator side.
No functional change.
|
| |
|
|
| |
Update basic profile to use the replaceable interface, making configuration less error-prone. Add support to query avatar's home user account and profile service for regions usng the updated OpenProfileModule with Hypergrid.
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
| |
of OSHttpRequest/OSHttpResponse.
This is required for the substitution of different HTTP servers or the newer HttpServer.dll without having to commit to a particular implementation.
This is also required to write regression tests that involve the HTTP layer.
If you need to recompile, all you need to do is replace OSHttpRequest/OSHttpResponse references with IOSHttpRequest/IOSHttpResponse.
|
| |
|
|
| |
wide use will have to wait a few releases. So the sims are still calling GET for now.
|
| | |
|
| |
|
|
|
|
|
| |
SendCreateChildAgent" message
This is misleading since a simulator will call this method before successfully trying remote regions.
Also comments out spammy "[SIMULATION]: Stream handler called" AgentHandlers messages for now.
|
| |
|
|
|
|
|
| |
57956c4b-ff2e-4fc1-9995-613c6256cc98>: Invalid character 'O' in input string messages
These are just the result of an attempt to canonicalize received messages - it's not important that we constantly log them.
Also finally get the deregister grid service message working properly
|
| |
|
|
| |
deregister region message
|
| |
|
|
| |
(e.g. 1000, 1000) rather than meter positions (256000, 256000)
|
