request frenzy: upgrade/alternative to http request trigger
Posted: 17 May 2016 18:14
I like the http request trigger, as it makes it possible to easily send a signal to the mobile device, and have it respond to it any way one likes.
The part I don't like about it is that a request must be http-ish. This lacks the flexibility which is possible with for example inetd daemon.
Many busybox binaries for Android provide a stripped down version of an inetd, but frankly, I never managed to let it respond properly on Android -but even then it lacks the direct link to execution of an Automagic flow.
It seems that, with the http server in Automagic, most of what is needed for an inetd look/work-alike already exists. I'd like the http server to not only accept http-kind of requests, but also plain no-protocol data exchange as is possible with inetd: bind listener to a port, put incoming request in a variable, trigger, send flow output back through port. tcp only may be sufficient.
The part I don't like about it is that a request must be http-ish. This lacks the flexibility which is possible with for example inetd daemon.
Many busybox binaries for Android provide a stripped down version of an inetd, but frankly, I never managed to let it respond properly on Android -but even then it lacks the direct link to execution of an Automagic flow.
It seems that, with the http server in Automagic, most of what is needed for an inetd look/work-alike already exists. I'd like the http server to not only accept http-kind of requests, but also plain no-protocol data exchange as is possible with inetd: bind listener to a port, put incoming request in a variable, trigger, send flow output back through port. tcp only may be sufficient.