wiki:BluePrint/Messaging/Parsing

Version 3 (modified by Fran Boon, 13 years ago) ( diff )

--

Inbound Message Parsing

Table of Contents

  1. Inbound Message Parsing
  2. Introduction
  3. Where should the code live?
  4. Parsing
  5. Use Cases

Introduction

This is a project proposal for GSoC 2012. We need to parse inbound messages, with an initial focus being SMS.

We can test this with ​Clickatell or a local phone (the Clickatell Inbound SMS fucntionality needs to be developed, which could be in-scope for this project).

Where should the code live?

Currently message parsing is done in the core code: ​modules/s3/s3msg.py

We want to be able to make this a deployment-specific set of options.

We are still working on developing our ​Profile Layer for having deployment-specific files separated from core code, so we can start by just making this a deployment-template like ​000_config.py copying the file to modules/s3/s3parsing.py for easy import into S3MSG.

Parsing

If we need to have complex parsing, then we can make use of pyparsing

  • wiki/BluePrint/Messaging#Parser

Use Cases

This will be used by at least CERT. They wish to process responses to deployment notifications where the recipients send back at least 'Accepted' / 'Reject'

Note: See TracWiki for help on using the wiki.