Thank you very much!
In order of importance: HTTP 1.1, HTTP 1.0, HTTPS
I can see a command line interface as useful, but I think that would be a
separate project that would rely on the grizzly API.
Also, please add the ability to easily handle long running comet
connections, i.e. where the client does not close the connection after
sending the request but continues to receive data from the server over a
long period of time.
Kedar Mhaswade wrote:
>
> - What is the current inclination of this community about *existing* http
> client programs? (examples: cURL, wget)
>
> - A command line is necessary (something like grzget) but an API is more
> important, correct?
>
> - Suppose I were to do a command line, I'd like to stick to an existing
> and robust command line interface (e.g. cURL) so that users don't have
> to learn anything new.
>
> - Number of protocols -- this is an on-going task because we will support
> a number of protocols as we make progress. But to begin with, the first
> release of this library/CLI should support HTTP/HTTPS/FTP with
> necessary
> support via proxies and various authentication policies.
>
> I'd utilize community response here and commit to a spec in a few days :)
>
--
View this message in context: http://www.nabble.com/Looking-for-HTTP-client-examples-tp19853693p20197873.html
Sent from the Grizzly - Users mailing list archive at Nabble.com.