support callbacks in responses about smssync

[eyedol]

You mind sharing a use case for this feature?

[mandric]

I will get back to you soon.

[eyedol]

Thank you mandric -- looking forward.

[mandric]

Hey again, the use case is referrals. Basically want the data in one sms message to get parsed and forwarded to another destination depending on the data inside of it. The use case is likely very specific to our needs/constraints. We are deploying on CouchDB and so there are limitations to what we can do server side with one request. We can create a record with an HTTP POST, but we can't do a join, we need to make another http request to look up a related record. So we need to send the gateway (or another process) some data about what is the next step to eventually complete a process, so we need to chain requests. There are two pieces to our stack: CouchDB and the SMS Gateway (SMSSync). So we are pushing extra process requests onto the gateway.

I'm planning to start a branch for this in my repo and see how it goes. If it's something you think is useful to the SMSSync users at large then let me know.

[mandric]

Oops closed by mistake.

[eyedol]

Yes, I think this well be really useful for most users. Could you send me a pull request when you're done with the implementation?

[mandric]

@eyedol I have it in a branch resp-callback2 in my repo. let me know what you think, it's somewhat quick and dirty, I wasn't expecting you to want to merge it, so let me know if you like the idea and how to clean it up. I also added callback processing to the task polling requests, but still testing it a bit.

Thanks!

[mandric]

@eyedol I branched from the 1.1.9 tag because there appeared to be a bug in master that wouldn't let me get off the settings screen. Also now I'm maintaining a 1.1.9-kujua branch because we need to do a release soon with the callback support. Let me know what you think, your comments would be greatly appreciated and thanks again for providing SMSSync. https://github.com/mandric/SMSSync/pull/1/files

I would use something like this to have the phone report back to the server whether the message was sent successfully or not.

(If sending at message fails at first, will SMSSync retry later?)

I would have needed it last weekend.

1. A message was sent to the SMSSync phone.
2. Message was parsed on the server, and a reply constructed and marked as sent.
3. SMSSync failed to receive the reply, so the whole thing failed silently.
   @mandric : Do you have installable apks?

[mandric]

@agenttihirvinen I do see: https://medic.s3.amazonaws.com/downloads/gateway/SMSSync-kujua2-debug.apk and I maintain a fork if you have issues over here: https://github.com/mandric/SMSSync/ currently the callback features are undocumented though. But basically you send a resp body with a json object that has options and data properties to configure the next http request, similar to the nodejs request module.

@mandric : Thanks, I'll try to find time to look into it. The apk fails to install btw on a Samsung Xcover at least.

[mandric]

@agenttihirvinen what version of Android? Also I assume you enabled non-market apps? ps. i don't want to create too much noise here if it's not related to resolving the ticket.

@mandric: I think it might have been an issue of not removing the old installation first, i.e. something to do with version numbers? Not really familiar with android development yet. =( Anyway, I'm now running a self-built instance of yesterday's state of development branch for multiple sync url support so I don't have to constantly break service or buy a new phone to use with my dev environment.

Any progress towards getting this merged?

[eyedol]

@mandric Did you get to implement this? I would like to look into this in the next release

[mandric]

Working on a port to 2.0 branch...

[mandric]

Tossed up a doc for this, there's a download link in there if you want to try it. Feedback appreciated... I only implemented what I needed but it might be good enough for generic use. https://github.com/mandric/SMSSync/wiki/HTTP-Callbacks

[eyedol]

@mandric I'll play with this tomorrow. Keep you posted

[eyedol]

@mandric is this still valid. Confirm so I can close it.

[mandric]

No it's not valid anymore. We are going with the more straightforward documented web API for results instead, see #11.