Nic Ferrier <[EMAIL PROTECTED]> wrote:
>
>> The only problem I know of HttpURLConnection is
>> that headers are stored in a Hashtable, so, it _might_
>> happen that one HTTP header might get lost...
>
> Are you sure? I thought that returning headers were stored in a
> vector? That's why there is this silly system of getHeaderField(int
> n).
Pretty sure... We ran into that problem while writing a HTTP proxying
servlet, and the site we were trying to proxy was using tons of Cookies.
Basically we ended up using another HTTP stack...
> I tried for a while to add the concept of default headers that get
> picked up properly to the Kaffe HttpURLConnection... I gave up in the
> end because the scheme was so rubbish.
>
> In general I think HttpURLConnection is bad design... but it does the
> job.
The whole java.net doesn't satisfy me at all... Like adding protocol
handlers, you can do it just once, in you whole VM... It wasn't designed by
the "master" (James Gosling) and you can totally tell...
Pier
--
----------------------------------------------------------------------------
Pier P. Fumagalli Sun Microsystems <mailto:[EMAIL PROTECTED]>
___________________________________________________________________________
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff SERVLET-INTEREST".
Archives: http://archives.java.sun.com/archives/servlet-interest.html
Resources: http://java.sun.com/products/servlet/external-resources.html
LISTSERV Help: http://www.lsoft.com/manuals/user/user.html
