Kevin Harwell wrote: <snip>
Hmm now that I think about it, once all refs to the app goes away it will be destroyed. Upon reconnect it is not 'activated' but considered a new app. If we decide to put this in, my current opinion would be to keep it simple and just send a notification that the app was activated and whether or not it missed any messages. Then the app can retrieve any current state it might need to update itself with. This puts it in a position of knowing the current state which is consistent with when the app reconnects but is created new.
Here's a scenario where you can't recover state: DTMF digits being received from a channel. What should the application do in that case?
Ultimately this idea is formed around the assumption that all the state can be retrieved upon startup, so I'd scope out some use cases and see if that's true. Determine what state an application may need to keep and what can be gleamed from Asterisk. For example: do we provide a mechanism to know what channels are in the application, or does the application have to persist that themselves?
Cheers, -- Joshua Colp Digium, Inc. | Senior Software Developer 445 Jan Davis Drive NW - Huntsville, AL 35806 - US Check us out at: www.digium.com & www.asterisk.org _______________________________________________ asterisk-app-dev mailing list asterisk-app-dev@xxxxxxxxxxxxxxxx http://lists.digium.com/cgi-bin/mailman/listinfo/asterisk-app-dev
