WinProxy: No Decoder for GroupAPIv1

Description

// Banning a user

No Decoder for GroupAPIv1
{
'ban_action':i1, // Ban User
'ban_ids':
[
u<userUUID>
]
}
Please report this at http://jira.openmetaverse.org Be sure to include the entire message.

// Unbanning a user

No Decoder for GroupAPIv1
{
'ban_action':i2, // Unban User
'ban_ids':
[
u<userUUID>
]
}
Please report this at http://jira.openmetaverse.org Be sure to include the entire message.

// Information about the bans

No Decoder for GroupAPIv1
{
'ban_list':
{
'<userUUID>':
{
'ban_date':d"2015-07-17T03:42:48Z"
}
}
,
'group_id':'<groupuuid>'
}
Please report this at http://jira.openmetaverse.org Be sure to include the entire message.

Steps to Reproduce

None

Activity

Show:
Frederick Martian
November 27, 2015, 9:13 AM

I've been looking into this. Sending this is in principle already implemented in the Group Manger. However the code used for proxying won't be easy to extend to support this message since for the BanRequest message, the group id for which it is meant is encoded in the URL itself rather than part of the message. The message decoder as it is built now doesn't receive this information from the capability interface and therefore can't forward it further.
This would require a significant change of the whole message decoder, including extending the interface to add an optional parameter that can carry this information around.

Assignee

Unassigned

Reporter

Fly Man

Labels

None

Environment

All

Fixed in Revision

None

Components

Priority

Minor
Configure