Changes between Version 34 and Version 35 of BluePrint/Messaging


Ignore:
Timestamp:
05/09/10 18:47:31 (12 years ago)
Author:
Fran Boon
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • BluePrint/Messaging

    v34 v35  
    11= Blueprint for the Messaging Module =
    2 
    3 Current design is here:
     2Agasti design is here:
    43 * http://wiki.sahana.lk/doku.php?id=dev:msg_archi
    5 User Guide:
     4Agasti User Guide:
    65 * http://wiki.sahana.lk/doku.php?id=doc:message:english
    76
    87What we need is:
    98 * Contacts List
     9  * Just uses normal Groups & Persons?
     10  * Do we need to extend these at all? (to mark that they're used for a these purposes & have some logic to identify whether all members of a group have emails &/or SMS'able Tel#s. Mark the members when we get delivery failures?)
     11 * SMS Router
     12  * Routes incoming message according to whether it's using specialist micro-syntax (e.g. submitting an XForm to another controller)
     13  * Unidentified messages get sent to the Ticketing module's Master Message Log
     14 * SMS alerts (security alerts more common than natural disasters)
     15  * Being able to trigger an SMS alert broadcast upon reception of an SMS
     16   * Is this just an XForm to a Group? (Can we pre-populate the XForm to do this whenever a certain number is called or just a single word routes here?)
     17 * CAP alerts:
     18  * http://xml.coverpages.org/OASIS-CAPv11-200510.pdf
     19   * Use an XSLT?
     20   * http://code.google.com/p/pyedxl/source/browse/trunk/edxl/edxl.py
     21  * Subset of EDXL-DE: http://docs.oasis-open.org/emergency/edxl-de/v1.0/EDXL-DE_Spec_v1.0.pdf
     22  * http://talksahana.com/2009/03/04/firefox-browser-cap-alerting-plugin-sahana-idea-for-gsoc2009/
    1023 * Admin UI for:
    1124  * Email Settings
    1225  * SMS Settings
    13  * CAP alerts: http://talksahana.com/2009/03/04/firefox-browser-cap-alerting-plugin-sahana-idea-for-gsoc2009/
    14  * SMS alerts (security alerts more common than natural disasters)
    15   * Being able to trigger an SMS alert broadcast upon reception of an SMS
    1626 * SMS login / data entry / reports
    17  * [wiki:BluePrintMessagingModuleJ2ME J2ME client]
     27  * [wiki:BluePrintMessagingModuleJ2ME J2ME client]
    1828
    1929=== Core Architecture ===
    20 Instead of having several "apps" that cross-talk, such as sms, email, tweet, jabber, etc, it would be good to have a central messaging core that has 'connectors'. This would be the equivilient of a star-hub structure.
     30Instead of having several "apps" that cross-talk, such as sms, email, tweet, jabber, etc, it would be good to have a central messaging core that has 'connectors'. This would be the equivalent of a star-hub structure.
    2131
    2232This way, additional 'connectors' could be added or used as needed without refactoring the entire code base, and would allow sending messages from one connector to another, such as sms to email or email to jabber.