Status: pending implementation. Date: Jun 30 2004. Last revised:
Due to the modular and flexible architecture of RRFW, nothing prevents us from having the possibility of user messages displayed in RRFW pages. This design document describes the concept of this functionality.
The messaging subsystem will allow the RRFW users to leave comments and short messages directly at the RRFW pages. Those may be remarks about the graph contents, troubleshooting journal, etc.
Each user is uniquely identified by RRFW ACL susbsystem. We introduce several new attributes and privileges for messaging functionality. Privilege objects are the tree names.
Attributes:
The user's e-mail where the notifications will be sent
When set to true value, e-mail notifications will be sent to this users.
Privileges:
allows the user to add messages to the tree objects.
allows the user to see all messages for the tree
allows the user to receive e-mail notifications. For those notifications
generated by Messages, DisplayMessages
must be granted too.
allows the user to delete messages from the tree objects
allows the user to change any message
allows the user to change his/her own messages
The acledit
program will have two additional options that simplify
administration: --msguser
will grant all privileges except DeleteMessages
and EditMessages
, and --msgadmin
will grant all messaging privileges.
The messaging options database will contain parameters that each user can tune for himself or herself:
a) any new message in all trees; b) (default) new message for objects that I commented only.
a) plain text (default); b) HTML; c) RSS 2.0
The format pattern with keywords like $TREE
, $PATH
, $AUTHOR
,
$MSGID
, etc.
Default:
[rrfw $MSGID] $TREE $AUTHOR: $PATH
Each message will have the status of Read/Unread per each user in the system.
On the tree chooser page in RRFW Web interface, the user will be shown the unread messages.
RRS 2.0 feed will be provided for messages export and for integration with other messaging systems.
Copyright (c) 2004 Stanislav Sinyagin <ssinyagin@k-open.com>