| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
| |
AssemblyVersion("0.8.2.*")
|
| | |
|
| |
|
|
|
|
|
|
| |
completely inoperative.
This means the presence info may be out of date by up to 20 seconds, but this avoids scripts potentially triggering constants requests to user accout and presence info services.
Relates to http://opensimulator.org/mantis/view.php?id=7088 though I fixed in a different way.
Adds regression test for this case.
|
| | |
|
| | |
|
| |
|
|
| |
the heighmap of a region that does not exist.
|
| |
|
|
|
|
|
| |
stack.
Implement both LoadTerrain and StoreTerrain for all DBs.
Move all database blob serialization/deserialization into TerrainData.
|
| | |
|
| |
|
|
|
|
|
|
|
|
| |
allow different default regions for HG and direct grid logins.
This requires a new GridService.GetDefaultHypergridRegions() so ROBUST services require updating but not simulators.
This method still returns regions flagged with just DefaultRegion after any DefaultHGRegions, so if no DefaultHGRegions are specified
then existing configured defaults will still work.
Immediate use is for conference where we need to be able to specify different defaults
However, this is also generally useful to send experienced HG users to one default location and local users whose specified region fails (e.g. no "home" or "last") to another.
|
| | |
|
| |
|
|
|
| |
them next time asked. This keeps any estate settings from being reset
when the estate dialog is opened in a region with null estate storage.
|
| | |
|
| |
|
|
|
|
|
|
| |
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.
|
| |
|
|
| |
This prevents errors when one thread iterates over the regions (e.g., from RegenerateMaptileAndReregister()) while another thread is adding a region.
|
| |
|
|
| |
Restrict IPresenceData.VerifyAgent to only return bool result
|
| | |
|
| |
|
|
|
|
|
|
|
| |
parcel owner ID to the estate owner even if the group UUID was present.
Aims to address http://opensimulator.org/mantis/view.php?id=6355
As part of this work, an incomplete IXGroupsData was added which currently only allows store/fetch/delete of group records
(i.e. no membership data etc)
This is subject to change and currently only an in-memory storage implementation exists for regression test purposes.
|
| |
|
|
| |
have an AssemblyInfo file.
|
| |
|
|
|
| |
This was not necessary with the nant build but is for xbuild, since xbuild includes associated project DLLs
And so picks up OpenMetaverse.dll even though it isn't referenced by OpenSim.Data.Null.dll
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
includes database region store migrations for mssql, mysql, sqlite
enable/disable this module:
Cap_EnvironmentSettings = "localhost" (for enable)
Cap_EnvironmentSettings = "" (for disable) at ClientStack.LindenCaps section (OpenSimDefaults.ini file)
or owerwrite in OpenSim.ini
mantis: http://opensimulator.org/mantis/view.php?id=5860
Signed-off-by: BlueWall <jamesh@bluewallgroup.com>
|
| | |
|
| | |
|
| |
|
|
|
|
|
| |
for granting rights via a module call.
Rename IFriendsModule.GetFriendPerms() -> GetRightsGrantedByFriend() to be more self-documenting and consistent with friends module terminology.
Add some method doc.
|
| |
|
|
|
| |
This required an option to be added to NullRegionData via ConnectionString for it to act as a non-static instance, so that regression tests (which only load this class once) don't get hopeless confused and complex to compensate.
Normal standalone operation unaffected.
|
| | |
|
| |
|
|
| |
of the simulator expect
|
| |
|
|
|
|
| |
5035).
Using the RemoteAdmin API to close then recreate a region would fail if the estate name had not changed. If the estate name /was/ changed then the existing estate would be renamed rather than a new one being created. The problem really arose from a lack of distinction in the data storage layer between creating new estates and loading existing ones.
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
security to friendship identifiers so that they can safely be deleted across worlds. Had to change Get(string) to use LIKE because the secret in the identifier is not always known -- affects only HG visitors. BOTTOM LINE SO FAR: HG friendships established and deleted safely across grids, local rights working but not (yet?) being transmitted back.
|
| |
|
|
| |
FriendsData[] GetFriends(string principalID) to IFriendsData and FriendInfo[] GetFriends(string PrincipalID) to IFriendsService. Refactored some more in the FriendsModule. Made client get notification of local friends permissions upon HGLogin. HG Friends object permissions work.
|
| |
|
|
| |
correctly handled. Friends list showing correct foreign names. TODO: GrantRights.
|
| | |
|
| |
|
|
| |
IEstateDataStore.GetEstatesByOwner(UUID)
|
| |
|
|
| |
Thanks MisterBlue...
|
| |
|
|
| |
static dictionaries on NullUserAccountData instance instead to stop user accounts being carried over between tests
|
| |
|
|
| |
The in-memory storage of region data that is used by default with SQLite now handles wildcards in region names in the same way as SQL queries do with other databases.
|
| |
|
|
| |
from a region and allow normal day cycles to be reestablished
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
| |
OpenSim.Data.Null.UserAuthenticationData plugin
additional tweaks to get this working properly
|
| |
|
|
|
|
| |
stored in regionsettings. Upon generation of a new tile image, the old one is deleted. Tested for SQLite and MySql standalone.
* Fixed small bug with map search where the local sim regions weren't found.
|
| |
|
|
|
|
| |
home and position info in the presence service. WARNING: I violated a taboo by deleting 2 migration files and simplifying the original table creation for Presence. This should not cause any problems to anyone, though. Things will work with the new simplified table, as well as with the previous contrived one. If there are any problems, solving them is as easy as dropping the presence table and deleting its row in the migrations table. The presence info only exists during a user's session anyway.
BTW, the Meshing files want to be committed too -- EOFs.
|
| |
|
|
| |
changes in IUserAccountService, just the data layer.
|
