| Commit message (Collapse) | Author | Files | Lines |
|---|
|
Currently they aren't plugin modules as the support for dynamically loading them isn't complete.
|
|
|
|
multiple duplicates of the same code.
|
|
OpenSim/Data/DataPluginFactory.cs
- removed dependencies on a few executable assemblies in
bin/OpenSim.Data.addin.xml
- trim trailing whitespace
|
|
in the UUID field instead of the actual UUID because of an implicit use
of ToString()
|
|
some of our DNS/dotted decimal issues that plague teleporting.
We are increasing the MajorInterfaceVersion from 1 to 2 in the
gridserver, so sims will need to be updated on various grids.
|
|
it fails to implement the required OGS interface version
|
|
r7676.
NOTE: Changes UGAIM.
|
|
All the other caps (except the initial one) are already sent with hostname
instead of IP.
NOTE: This changes gridserver and userserver
|
|
- Added remoting_port to the non-fast if-branch, too
- Added httpPort field to map_blocks response. This isn't needed yet, but will be for correct crossing between regions.
Note: This touches the GridServer.
|
|
libOMV.
|
|
release a direct descendant of the stable 7364, with all the features and
none of the issues.
This omits the following patch chain: r7383 r7382 r7381 r7377 r7375 r7373
r7372 r7370 r7369 r7368 r7367 r7366
|
|
* Update libopenjpeg as well for this patch.
* Appears to be okay on a very short sniff test
* Source code will be placed in opensim-libs shortly
|
|
https://lists.berlios.de/pipermail/opensim-dev/2008-November/003468.html
* This is done by sending a 'major interface version' number on sim registration. Developers must increment this every time they make a change that would make the previous
OpenSim revision failure incompatible with the new one (non-fatal incompatibilities are fine).
* This number resides in OpenSim.Framework.Servers.VersionInfo.MajorInterfaceVersion
* This allows the grid service to stop older, incompatible regions from connecting
|
|
some trailing whitespace.
|
|
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
|
|
- 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.
|
|
* Updated MSSQL to reflect resend changes
* Added the new columns in prims table.
* Created a implementation for getting gestures.
* Remove configurable table names for user.
* Thanks Ruud Lathorp
|
|
Corrects the spurious reference to MySQL namespace in
GridManager.cs.
|
|
* Updates to libomv r2243,
* Remove lots of unnecessary typecasts
* Improves SendWindData()
Thanks jhurliman.
* Will update OpenSim-libs in 10 minutes..
|
|
Thank you, RuudL, for a patch that brings MSSQL up to the same
implementation level as MySQL.
|
|
Thank you, Xugu Madison and ChrisDown, for a patch that
fixes linux filename extensions from .Xml back to .xml
|
|
* This is a HUGE OMG update and will definitely have unknown side effects.. so this is really only for the strong hearted at this point. Regular people should let the dust settle.
* This has been tested to work with most basic functions. However.. make sure you back up 'everything' before using this. It's that big!
* Essentially we're back at square 1 in the testing phase.. so lets identify things that broke.
|
|
Not enough logging. Added IP endpoing of request to the log
messages on lookup-failure
|
|
This patch adds some more informative logging if the region isn't found.
|
|
|
|
PluginLoader. Fix issue 1871.
|
|
|
|
|
|
attributes to external XML files. Fix issues 1682 and 1786.
|
|
(issue 1763).
|
|
region status check, so we can tell a bit better what the problem was
|
|
|
|
|
|
provide OSHttpRequest and OSHttpResponse to our REST handler.
also, this adds proper RestPlugin.IsGod() checking against the X-OpenSim-Godkey
HTTP request header.
last, i added XML doc comments to RestPlugin.cs
|
|
|
|
|
|
the status of the region using the region http uri just passed in
* If the status cannot be retrieved, then the region startup will terminate.
* The aim of this is for earlier detection of situations where the region can send messages out but cannot accept incoming requests (often due to firewall issues)
* This is currently an extremely simplistic check which completely trusts whatever http uri is given by the region
* This contact may be problematic, though since the user service needs to be able to contact the region http uri, it doesn't seem unreasonable for the grid to have to be able to do so too at this stage
* This change will require a prebuild
|
|
* This in preparation for further login validation to check that the region logging in is properly contactable.
* Also increase verbosity of some error messages
|
|
startup will now terminate instead of carrying on (and thus burying the error message)
|
|
|
|
dispatch for now
|
|
|
|
|
|
|
|
* Made a bunch more members static, removed some dead code, general cleaning.
|
|
(this took a while to run).
|
|
when they were.
* A few things for testing.
* This makes a modification to the region registration with the grid server so that the region can send it a chosen password to identify itself. It will not cause any errors, if either one are not updated.
|
|
:: Believe it or not, but INSERT/UPDATE is actually a better pattern than REPLACE, since, with INSERT/UPDATE you can catch erroneous UPDATES to non-INSERTed items as well as catch erroneous re-INSERTS. in 95% of the cases, you SHOULD have a clear INSERT context, and a clear and separate UPDATE context. If you think your case falls within the 5%, maybe you should re-evaluate your code. ::
|
|
|
