[Info-vax] API/RTL providing cURL-esque functionality

[Richard Maher]

On 1/2/2016 12:02 PM, David Froble wrote:
>
> So, you know the URLs or IP addresses that you want to contact?  Sounds
> more like your app will be the client.

A server to HTML5 Javascript clients will become a client to Google 
Cloud Messaging at sometime in the future as it wishes to tell the 
previously registered client that event X has occurred and potentially 
wake it up via Service Worker.
>
> Now I'm assuming, and that's always dangerous, that those you want to
> contact will accept inbound TCP/IP connection requests.  If so, then you
> would request a connection, if successful send your data in whatever
> operation is appropriate, POST, GET, OTHER, get back whatever reply is
> appropriate, and close the connection.
>

I can write TCP/IP socket apps with a functional result metric at the 
top of the game. As you've seen though I need TLS and don't want to 
re-invent the Socket re-use algorithms and HTTP 1.2 headers and hand-shakes.

Hopefully VSI will include a $QIO interface that adds TLS to all send 
and receives on a channel when they rewrite UCX?