Sparty's Turn to Get Big Update

=> My CLI client for the spartan protocol has been updated in a huge way.

It now works very similarly to gemcall:

• It can be used as either a lib or a CLI tool.
• It supports streaming responses from the server.

The spartan protocol doesn't have any encryption, so there's a lot of stuff gemcall has that sparty can't use. On the other hand spartan supports data transfer from client to server, and sparty supports three different ways of providing that data:

• The QUERY STRING portion of a URL is automatically sent as data input.
• OR you can use the --message argument followed by a string.
• OR you can use the --inputfile argument followed by a filepath, and this file will be sent.

I ripped a lot of logic from gemcall, because I like how I solved things there. You call the request function and get a Response object back, which wraps the socket and provides the response code and meta field for your disposal.

-- CC0 ew0k, 2021-07-14