Changes between Version 12 and Version 13 of BluePrint/Messaging/Parsing


Ignore:
Timestamp:
04/01/12 12:46:13 (10 years ago)
Author:
Fran Boon
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • BluePrint/Messaging/Parsing

    v12 v13  
    2121Before exiting those threads, it should trigger a new Schduled task (once, now) to do the parsing.
    2222
    23 Tropo, however, is different, since that receives inbound connections to it's controller.
    24 
    2523All Parser Workflows should be defined in tasks.py.
    2624
    2725The Configuration links these Tasks to Inbound Sources, along with any other args, in a new msg_workflow table.
     26- so this can be linking 2 FKs in the scheduler_task table
     27
     28Tropo, however, is different, since that receives inbound connections to it's controller.
     29In order to make this consistent a schduled task can be created but set to never run on schedule & have that run from the controller (or, even better, have this run the same code that the schduled task runs but inline...since this will be pretty much a no-op other than triggering the parser, so won't hold the Tropo connection up & avoids having to spawn a new thread).
     30
     31
    2832== Parsing ==
    2933We want to be able to process [wiki:BluePrint/Messaging/OpenGeoSMS OpenGeoSMS]