Today I was investigating the use of a PUSH subscription (HTTP POST) to notify some other application about the results of their job.
This application (SAS) needs a quite specifically formatted XML-body to understand my message. I was unable to parse this from a XMLTemplater and textwriter in the workspace, through a notification, to the body the PUSH subscription sends to the provided URL.
The alternative was a more text-like body, I could easily get to the subscription, Only that needed to be presented as an application/x-www-form-urlencoded contend type. A content type the push subscription does not support.
I ended up making a workspace subscription and a small workspace with a HTTPCaller converting the subscriber_content to the desired body format. This is a bit like building the PUSH Subscription service I would like to see.
Would it be an idea to upgrade the PUSH subscription, give it some more content-type methods (perhaps even more REST methods) and a template for the body and perhaps for the URL? Like a mini-HTTPCaller / XMLTemplater / JSONTemplater combination?
Kind regards,
Martin
