Bug #6950
closed
Missing connection notification handling
Added by krileon almost 7 years ago.
Updated almost 7 years ago.
Start date:
27 December 2017
Description
There's no notification stream handling for connection activity. This means sending a notification for pending connection request, etc.. would have to use a database stored title/message.
This should handle the following usages.
profile.USER_ID.connection.CONNECTION_ID = OWNER is connected to USER_ID (CONNECTION_ID optional)
profile.USER_ID.connection.CONNECTION_ID.pending = OWNER sent pending connection request to USER_ID
profile.USER_ID.connection.CONNECTION_ID.accepted = OWNER accepted connection request from USER_ID
profile.USER_ID.connection.CONNECTION_ID.rejected = OWNER rejected connection request from USER_ID
For notifications when it's a pending request output xsmall buttons to accept or reject the request directly from notifications.
The connection_id isn't needed so use the below to handle state.
profile.USER_ID.connection
profile.USER_ID.connection.pending
profile.USER_ID.connection.accepted
profile.USER_ID.connection.rejected
- % Done changed from 0 to 70
Handling for the above assets is working. This includes buttons to Accept, Reject, and Cancel requests.
Still needs dynamic notification connection state handling. What that means is if profile.USER_ID.connection notification is logged it should check the current connection state and adjust the notification accordingly.
- Status changed from Assigned to Resolved
- % Done changed from 70 to 100
Opted to skip implementation of dynamic state checking as it's just too heavy and unnecessary.
- Target version changed from 892 to 4.2.0
- Status changed from Resolved to Closed
Also available in: Atom
PDF
Updated by