Changes between Version 2 and Version 3 of BluePrint/Messaging/Parsing
- Timestamp:
- 03/13/12 17:40:31 (13 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
BluePrint/Messaging/Parsing
v2 v3 1 == Inbound Message Parsing == 2 [[TOC]] 3 == Introduction == 1 4 This is a project proposal for GSoC 2012. 2 3 5 We need to parse inbound messages, with an initial focus being SMS. 4 6 5 We can test this with [http://www.clickatell.com/pricing/us_small_business.php Clickatell] or a local phone (the Clickatell Inbound SMS fucntionality needs to be developed ).7 We can test this with [http://www.clickatell.com/pricing/us_small_business.php Clickatell] or a local phone (the Clickatell Inbound SMS fucntionality needs to be developed, which could be in-scope for this project). 6 8 9 == Where should the code live? == 7 10 Currently message parsing is done in the core code: [https://github.com/flavour/eden/blob/master/modules/s3/s3msg.py#L192 modules/s3/s3msg.py] 8 11 … … 11 14 We are still working on developing our [https://groups.google.com/forum/?fromgroups#!topic/sahana-eden/Vy8xT4bA_pA Profile Layer] for having deployment-specific files separated from core code, so we can start by just making this a deployment-template like [https://github.com/flavour/eden/blob/master/deployment-templates/models/000_config.py 000_config.py] copying the file to {{{modules/s3/s3parsing.py}}} for easy import into S3MSG. 12 15 16 == Parsing == 13 17 If we need to have complex parsing, then we can make use of [wiki:pyparsing pyparsing] 18 * wiki/BluePrint/Messaging#Parser 14 19 15 20 16 This will be used by at least [wiki:BluePrintCERT CERT] 21 == Use Cases == 22 This will be used by at least [wiki:BluePrintCERT CERT]. 23 They wish to process responses to deployment notifications where the recipients send back at least 'Accepted' / 'Reject'