Not giving ourselves enough credit on the home page

[Eric Johnson <er...@tibco.com>]

Based on the recent URI discussion, and some other points, it strikes me 
that we could take a little more credit for the work that has gone into 
HttpClient.

On the HttpClient home page 
(http://jakarta.apache.org/commons/httpclient/index.html) four RFCs are 
listed.

Given all the discussion about URIs being thrown around, I think it 
might be reasonable to add RFC 2396 - for URI compliance.  Then there is 
RFC 1867, for multipart/form-data POST requests (I think I got the right 
number there).  Are there RFCs corresponding to our "cookie" compliance? 
 Any other RFCs we can claim credit for conforming to?

With the recent "Protocol" changes, I think we've made it relatively 
straightforward for clients of HttpClient to plug in their own secure 
sockets implementations, making it easier to use third party, non-Sun 
solutions.

Someone posted recently that HttpClient appears to be faster than the 
corresponding Sun solution.

Any other up-sides that people can think of?  To push adoption of 
HttpClient, I think we want to get as much up on this page as we can. 
 Not to mention, the next time my boss comes and asks me exactly why 
I've been sinking time into HttpClient, I can point to this page, and 
ask "what's not to like?"

Just a thought.

-Eric.

Re: Not giving ourselves enough credit on the home page

[Jeffrey Dever <js...@sympatico.ca>]

All good points.  I had not yet had a chance to update those documents. 
 Its great to have input from everyone as the content is the hardest part.

I created a bug report for it and am refrencing back to this mail thread.
http://issues.apache.org/bugzilla/show_bug.cgi?id=16625

BTW: anyone can submit patches to the xdocs as well as the java files!

-jsd


Eric Johnson wrote:

> Based on the recent URI discussion, and some other points, it strikes 
> me that we could take a little more credit for the work that has gone 
> into HttpClient.
>
> On the HttpClient home page 
> (http://jakarta.apache.org/commons/httpclient/index.html) four RFCs 
> are listed.
>
> Given all the discussion about URIs being thrown around, I think it 
> might be reasonable to add RFC 2396 - for URI compliance.  Then there 
> is RFC 1867, for multipart/form-data POST requests (I think I got the 
> right number there).  Are there RFCs corresponding to our "cookie" 
> compliance? Any other RFCs we can claim credit for conforming to?
>
> With the recent "Protocol" changes, I think we've made it relatively 
> straightforward for clients of HttpClient to plug in their own secure 
> sockets implementations, making it easier to use third party, non-Sun 
> solutions.
>
> Someone posted recently that HttpClient appears to be faster than the 
> corresponding Sun solution.
>
> Any other up-sides that people can think of?  To push adoption of 
> HttpClient, I think we want to get as much up on this page as we can. 
> Not to mention, the next time my boss comes and asks me exactly why 
> I've been sinking time into HttpClient, I can point to this page, and 
> ask "what's not to like?"
>
> Just a thought.
>
> -Eric.
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: 
> commons-httpclient-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: 
> commons-httpclient-dev-help@jakarta.apache.org
>
>

Re: Not giving ourselves enough credit on the home page

[Ortwin Glück <or...@nose.ch>]

Mike Moran wrote:
> http://www.innovation.ch/java/HTTPClient/urlcon_vs_httpclient.html

Interesting fact:

Oracle is using this library for their application server. They ship it 
also with the Oracle 9i Client. It can be found in 
$ORACLE_HOME/lib/http_client.jar.

Maybe one day they will change to our baby? ,-)

Re: Not giving ourselves enough credit on the home page

[Mike Moran <mi...@mac.com>]

Eric Johnson wrote:
[ ... ]

>
> Someone posted recently that HttpClient appears to be faster than the 
> corresponding Sun solution. 

I don't think Sun's is the one to beat. The innovation.ch one is not 
bad, though getting pretty old. You may want to do a comparison with 
what the jakarta one can do based on:
http://www.innovation.ch/java/HTTPClient/urlcon_vs_httpclient.html

In particular, the inability to set a timeout on requests is a 
show-stopper for any serious use of Sun's implementation.

-- 
Mike