| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
Resolves http://opensimulator.org/mantis/view.php?id=6937
|
|
|
|
|
|
|
|
| |
use for fetching group data to be different from im.fromAgentID
This is because xmlrpcgroups currently always checks visibility for the requesting agent ID (unlike Groups v2, which can accept UUID.Zero)
But group notice IMs have a from agent which is the group rather than the sending agent.
Further addresses http://opensimulator.org/mantis/view.php?id=7037
|
|
|
|
|
|
|
|
| |
group chat to avoid timeout issues when sending messages to large groups.
Only implementing for XmlRpcGroups initially to test.
May require MessageOnlineUsersOnly = true in [Groups] to be effective.
In relation to http://opensimulator.org/mantis/view.php?id=7037
|
| |
|
| |
|
|
|
|
| |
instead of "all" because some paths in the code assume there's a UUI in the RequestingAgent string.
|
| |
|
|
|
|
| |
for group chat.
|
|
|
|
| |
or else they'll see an echo of their own messages after teleporting.
|
| |
|
|
|
|
|
|
| |
join/drop appropriately, invitechatboxes.
The major departure from flotsam is to send only one message per destination region, as opposed to one message per group member. This reduces messaging considerably in large groups that have clusters of members in certain regions.
|
| |
|
|
rest to Addons.Groups.dll.
|