Changes between Version 75 and Version 76 of BluePrint/Messaging

Timestamp:

06/17/10 19:05:39 (15 years ago)

Author:

Fran Boon

Comment:

msg_outbox

BluePrint/Messaging

@@ -23 +23 @@
 
 === How do we achieve this? ===
- * Table {{{msg_log}}} is used as a replacement for the current {{{msg_inbox}}}, {{{msg_outbox}}} & {{{ticket_log}}}.
+ * Table {{{msg_log}}} is used as a replacement for the current {{{msg_inbox}}} & {{{ticket_log}}}.
   * Fields: sender, subject, body, verified, actionable, assignee (multiple?), actioned, priority
    * Q: Do we move some of these 'ticketing' fields to a separate, linked {{{ticket_msg}}} table?
@@ -38 +38 @@
   * Subscriptions can be viewed from the user's subscriptions page
    * Add to 01_menu.py & pr.py
- * Table {{{msg_delivery_status}}} is used to store delivery statuses.
+ * Table {{{msg_outbox}}} is used to identify messages which need to be routed externally & store delivery statuses.
   * Fields: message_id, pe_contact_id, status
  * Table {{{msg_read_status}}} is used to show that a message has been read by a user.
@@ -46 +46 @@
  * Parser has hooks for modules to plug-into?
  * Q: Do we treat a pentity the same way as any other resource?
-  * Just that when a message is routed to them, it not only tags but also creates an entry in {{{msg_delivery_status}}}, which is scanned by the Cron task for 'pending' messages to be sent out.
- * {{{ shn_rest_controller()}}} is modified to check msg_log for messages tagged to the resource (list) or record (display/update)
+  * Just that when a message is routed to them, it not only tags but also creates an entry in {{{msg_outbox}}}, which is scanned by the Cron task for 'pending' messages to be sent out.
+ * {{{shn_rest_controller()}}} is modified to check msg_log for messages tagged to the resource (list) or record (display/update)
   * Views modified as above
  * 'Ticketing Module' UI