SynthMakerrl ·
The HTTP Post module can only send HTTP requests. The server's answer currently is lost in the depths of the module. It shouldn't be too hard to implement since the answer just has to be brought to the outside.
To make something useful with the module it needs three additional outputs: - an int output that contains the HTTP Status Code (200, 404, 503,... you get the idea) - a String output that contains the HTTP response header (or as two String Array outputs for names and values - like the inputs) - a String output of the HTTP response data. According to the content type it could be ascii or "pseudo hex" encoded (as the String to Sys-ex module works, like 3AFC00D7...)
This way _real_ communication to a webserver could be implemented. - (I'm not asking for SSL and HTTPS - yet) - Also missing: the request headers cannot be set (important for sending back cookies) - User-Agent is "Posting" ?? - better let specify the agent through the request headers
IT seems the HTTP Post module is implemented following the assumption that the body of the post request only holds key/value pairs (the 2 input arrays 'names' and 'values'). But that's just an artificial limitation (e.g. multipart-form requests look differently) and in principle a HTTP Post body can contain any kind of binary data.
Not tested yet, does the HTTP Module follow redirects (301, 302, 303)?
There is a bug. After the first successful request, the boolean output stays always true.
----
And it would be very useful to offer at least some basic UDP networking (a UDP listener task, and the possibility to send datagrams to a server:port) This way at least basic OSC (open sound control) could be implemented.
Thank you for listening.