curlreplacement -- the scope of HTTP requests that Osmos will create are limited. Generalized authentication handshakes, forwarding data from a previous API request to the next one, and non-HTTP (TCP, FTP, Telnet) are not supported by this connector.
www.example.com/weather?city=seattle. Let's say that issuing a
GETrequest to this endpoint returns an array of temperature measurements -- one measurement for every hour of the day. Something like this:
GETrequest from an Osmos source would result in 24 records, one for each of the above numbers, being fed into the pipeline. You may also choose to have these 24 numbers treated as one record with 24 fields in it.