You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Do you not find most of the work associated with twilio etc are setting up state machines and database layers for the sms/call states? In my experience the "send" portion of the work is very small compared to the data tracking and for twilio for instance setting up hooks to either get the delivery status or polling to do so.
I think it for sure deserves probably an engine to be mounted at routes, and persisting it out (even for interceptions for invalid numbers, as you suggested). that’s actually a huge feature, and VERY nice to have.
probably, something like
# on routes.rb
mount ActionMessage::Statistics => '/sms'
This engine would define two routes, one for hooks for the adapters to post messages into (such as Twilio). and the other one for statistics (more on that the statistics part on another github issue);
we’d probably have a module to include on the tracker model under the app for Mongoid, and a generator for SQL databases (generates both migration and model);
and on the hook action, we’d record every single interaction out the adapters send for us under that model. Would be basically plug and play.
The text was updated successfully, but these errors were encountered:
Do you not find most of the work associated with twilio etc are setting up state machines and database layers for the sms/call states? In my experience the "send" portion of the work is very small compared to the data tracking and for twilio for instance setting up hooks to either get the delivery status or polling to do so.
I think it for sure deserves probably an engine to be mounted at routes, and persisting it out (even for interceptions for invalid numbers, as you suggested). that’s actually a huge feature, and VERY nice to have.
probably, something like
This engine would define two routes, one for hooks for the adapters to post messages into (such as Twilio). and the other one for statistics (more on that the statistics part on another github issue);
we’d probably have a module to include on the tracker model under the app for Mongoid, and a generator for SQL databases (generates both migration and model);
and on the hook action, we’d record every single interaction out the adapters send for us under that model. Would be basically plug and play.
The text was updated successfully, but these errors were encountered: