| Commit message (Collapse) | Author | Files | Lines |
|---|
|
descriptive of what it actually does
|
|
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.
|
|
|
|
http://opensimulator.org/mantis/view.php?id=2361 that allows region registration to be enabled/disabled on the grid server
* Region registration is enabled by default in the configuration unless the user chooses otherwise
* On the console
* show status - shows grid status
* enable-reg - enables region registration to the grid
* disable-reg - disables region registration
* Enabling or disabling region registration will not affect any other grid functions or regions already on the grid
|
|
- Some formatting cleanups
|
|
|
|
when estate_settings.xml is empty or missing
|
|
Note: New file, run prebuild.
|
|
|
|
|
|
is not necessary.
|
|
immedietly.
|
|
* Experimenting with the PacketPool mechanism.
* It's still disabled in the code, however there's now a flag to enable it.
* Converted to use Generic Collections vs Hashtables, also now uses a list of 'OK to pool' packets, starting with the high volume PacketAck packet.
|
|
|
|
|
|
|
|
the new surface touch parameters in 1.21 viewers.
|
|
for the new surface touch parameters in 1.21 viewers.
TODO: add the touch args to OnGrabObject and OnDeGrabObject.
|
|
|
|
|
|
|
|
|
|
* Implmements llModifyLand() and a check for the "Allow others to terraform flag"
* Thanks tglion!
|
|
fields is GONE (HttpServer does not support that), you can read the
"normal" HTTP headers available via properties, and you can add
headers. also, it is now possible to set a timeout for KeepAlive (for
those clients that pay attention to it).
this also fixes the broken REST inventory/assets/appearance services,
they should be working again.
testcase for OSHttpResponse will follow.
|
|
|
|
* I believe this was the cause of the remaining packet_out_of_order messages in the Linden client logs
* There were race conditions where multiple clientstacks would overwrite each other's sequence numbers
|
|
case for OSHttpRequest (not very fancy yet, but still).
|
|
adding default_loginLevel in USerServer.xml to set a default
login level to acces to the grid. Fixing one bug in login_reset
|
|
|
|
|
|
Implementation of llModifyLand() and There is a bug on
permission-check of land-terraforming: x an y-coordinates
are interchanged on function-call ExternalChecksCanTerraformLand.
Correct: x is west, and y is north. 2) Missing check of
"Other allow to terraform-flag" (Parcel.ParcelFlags.AllowTerraform)
|
|
|
|
* Initial implementation
* You'll only be able to seen green dots on regions on the map that have been updated.
|
|
gets lost on teleport.
|
|
|
|
|
|
and string type = "". Currently we are down to 14 warnings
in the VS2005 C# build which is pretty good.
|
|
Thise were client supplied untrusted values we never used anyway.
|
|
|
|
- Added lookup in the data-layer
- MySQL works
- SQLite doesn't have a grid-db, so it won't work there
- I added MSSQL-code to the best of my knowledge; but I don't know MSSQL :-)
- Added the plumbing up to OGS1GridServices. This speaks with the grid-server
via XMLRPC.
- Modified MapSearchModule to use the new data. It's backward compatible; if
used with an old grid-server, it just returns one found region instead of a
list.
- Refactored a bit.
Note: This updates data, grid-server and region code. No new files.
|
|
|
|
StringWriter.Append() vs StringWriter.Append("\r\n"); StringWriter.Append() produces "\n" in *nix*
* This doesn't solve anything. Just gets the protocol right.
|
|
for consistency's sake
|
|
were appearing in the wrong order
|
|
to work anyway)
|
|
(which doesn't include stuff such as script starting time on the region server).
* Yes, you could work this out from timestamps in the logs, but that's far too much work
|
|
|
|
old way: each region module interested in chat from client had to
- subscribe to scene.EventManager.OnNewClient
- then in its OnNewClient delegate it would subscribe to
client.OnChatFromViewer to capture chat messages coming
new way: ChatModule is the only region module that uses the "old
way" approach but is now forwarding all client chat via
scene.EventManager.OnChatFromClient
- each region module interested in chat from client now only
subscribes to scene.EventManager.OnChatFromClient
this not only simplifies code, but also allows us to substitute
ChatModule with derived classes (ConciergeModule is going to be one
example).
Also, this changeset changes ChatFromViewer to ChatFromClient as it
doesn't necessarily have to be a viewer that is a chat source.
i've taken great care to only comment out those OnNewClient delegates
that were only used for getting at the client chat --- hope it's not
breaking anything.
|
|
|
|
Thank you, idb, for a patch to implement the packet and plumbing for
the material settings.
|
