| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
| |
http://opensimulator.org/mantis/view.php?id=2843
|
|
|
|
|
|
|
|
| |
user for other users who are online.
* No need to send offline notifications since the client assumes this (and future clients should be able to do the same).
|
|
|
|
|
|
|
|
|
| |
is in the Tools menu available when editing an object
* This facility allows you to save changes to an object that you've rezzed into a region back into their original inventory item without having to take a copy of the rezzed
object.
|
|
|
|
| |
debug
|
| |
|
|
|
|
|
|
|
|
| |
- I first did lock on m_scenes for that access, but as m_scenes (currently) is
only changed in Initialise (and locked there), and PostInitialise is called
after the calls to Initialise, there shouldn't be a need to lock here.
- Trying out git-svn dcommit. Hope this works.
|
| |
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
| |
texture sending. Grain of salt not included.
|
|
|
|
|
|
| |
MessageTransferModule, much easier to understand (I hope).
|
|
|
|
|
|
| |
fromAgentSession field.
|
|
|
|
|
|
|
|
| |
the IM module and makes it into a module of it's own, which can be used by
all other modules. Removes some ugly hacks. Refer to the IM module to see
how it's used. Also fixes the persistence issue (Mantis #2598)
|
|
|
|
|
|
| |
client-thread. Will hopefully fix Mantis#2536.
|
|
|
|
|
|
|
| |
- Add tests for Util.isUUID
- First part of the fix for protocol interoperability between viewer 1.20 and 1.21 for friend offers.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
on-/offline updates, calling cards for friends.
This adds methods in the DB layer and changes the MessagingServer, so a full
update (incl. UGAIM) is necessary to get it working. Older regions shouldn't
break, nor should older UGAIM break newer regions, but friends/presence will
only work with all concerned parts (UGAIM, source region and destination
region) at this revision (or later).
I added the DB code for MSSQL, too, but couldn't test that.
BEWARE: May contain bugs.
|
|
|
|
|
|
|
|
|
|
| |
with the old Grid Instant Message over OGS1. Refactor the EventManager
to be independent of the rigid module structure design imposed by
the current implementation. Message routing is now done in the destination
module rather than in the event manager. This way, more or less granular
solutions are possible without core changes.
|
| |
|
|
|
|
|
|
|
| |
* 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.
|
| |
|
|
|
|
|
|
|
| |
* code caught lingering around with no real purpose other than causing warnings
will be taken down.
|
| |
|
|
|
|
|
|
|
| |
* You'll need to start-up the MessageingServer and set it up. It sets up like any of the other grid servers.
* All user presence data is kept in memory for speed, while the agent is online. That means if you shutdown the messaging server or the messaging server crashes, it forgets who's online/offline.
* Occasionally the region-cache will get stale if regions move around a lot. if it gets stale, run clear-cache on the messaging server console to clear the region cache.
|
| |
|
| |
|
| |
|
|
|
|
| |
.NET throws a different error then mono does. Thanks Melanie!
|
| |
|
|
|
|
|
|
|
| |
* Converted a large number of read-only fields to be actually, readonly.
* Reformatted code sections.
* Removed redundant code.
|
| |
|
| |
|
|
directory with any associated module-specific classes.
* Each module directory is currently inside one of the following category folders: Agent (Anything relating to do with Client<->Server communications.), Avatar (Anything to do with the avatar or presence inworld), Framework (Classes modules can use), Grid (Grid traffic, new OGS2 grid comms), Scripting (Scripting functions, etc), World (The enrivonment/scene, IE Sun/Tree modules.)
* This should be moved into a seperate project file.
|