Currently we just wait for stuff we recognise and then fire the deferred. This is a fairly crude way of going about it as most developers are likely to just ignore all that stuff and drop all the modem's signals on the floor.
As we start looking at backends I'd like a better way of handling those kinds of unsolicited responses so developers can hook into them.
Some modems send responses which are unsolicited, see http://www.developershome.com/sms/resultCodes3.asp for some examples. They're AT commands variations on soft interrupts.
Currently we just wait for stuff we recognise and then fire the deferred. This is a fairly crude way of going about it as most developers are likely to just ignore all that stuff and drop all the modem's signals on the floor.
As we start looking at backends I'd like a better way of handling those kinds of unsolicited responses so developers can hook into them.