tomcat-taglibs-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mark R. Diggory" <mdigg...@latte.harvard.edu>
Subject Re: What sucks about c:import!
Date Wed, 21 Aug 2002 15:20:40 GMT
The Jakarta Commons HttpClient has been usefull to me on a limited basis.

All I really use it for is for building "Multipart File Posts". And to 
do that I even had to use a Class someone wrote which is not in the 
HttpClient package right now. The nice thing about the package is that I 
can build a multipart requests off of files on the filesystem instead of 
byte[]'s in memory.

On the other hand, I've recently encountered issues with the responses 
being buffered either in memory or on the filesystem, which kinda sucks 
when all you want is to get an an InputStream on a really big XML file 
and SAX parse it.

So the HTTPClient library is a good package, but I see area's in need of 
improvement in it.

-Mark

Henri Yandell wrote:

>Isn't this the kind of thing that Jakarta Commons HttpClient specialises
>in? In which case a taglib for that would be a pretty nice affair...
>
>[I assume there's not one already..]
>
>Hen
>
>On Wed, 21 Aug 2002, Shawn Bayern wrote:
>
>  
>
>>Indeed - JSTL 1.0 does not support advanced HTTP operations from within
>>JSP pages using <c:import> (e.g., basic authentication, free modification
>>of headers), but a future version of JSTL could if there were enough
>>perceived need.  As Peter says, it's a good idea to inform the expert
>>group if you'd like to see this feature; the address is
>>
>>   jsr-52-comments@jcp.org
>>
>>--
>>Shawn Bayern
>>"JSTL in Action"   http://www.jstlbook.com
>>
>>On Wed, 21 Aug 2002, peter lin wrote:
>>
>>    
>>
>>>I'm assuming you want to get at things like cookies, user-agent and
>>>other http header data.
>>>
>>>you may want to make a request to the expert group, so that it is
>>>included in the next version of JSTL. I believe the current
>>>importsupport class just uses standard url & httpurlconnection classes.
>>>shawn will know more about the current implementation and where it might
>>>go in the future.
>>>
>>>
>>>peter
>>>
>>>
>>>"Mark R. Diggory" wrote:
>>>      
>>>
>>>>Now that I have your attention. We are continually working with managing
>>>>headers in our URL object requests to get resources from different
>>>>locations. Is there really any way I can set the request Header info on
>>>>the URL object being created by c:import? Right now I have my own custom
>>>>implementations to aquire such resources. I'd rather be able to use the
>>>>Standard Taglib.
>>>>
>>>>-Mark Diggory
>>>>Harvard-MIT Data Center
>>>>
>>>>--
>>>>To unsubscribe, e-mail:   <mailto:taglibs-user-unsubscribe@jakarta.apache.org>
>>>>For additional commands, e-mail: <mailto:taglibs-user-help@jakarta.apache.org>
>>>>        
>>>>
>>>--
>>>To unsubscribe, e-mail:   <mailto:taglibs-user-unsubscribe@jakarta.apache.org>
>>>For additional commands, e-mail: <mailto:taglibs-user-help@jakarta.apache.org>
>>>
>>>      
>>>
>>--
>>To unsubscribe, e-mail:   <mailto:taglibs-user-unsubscribe@jakarta.apache.org>
>>For additional commands, e-mail: <mailto:taglibs-user-help@jakarta.apache.org>
>>
>>
>>    
>>
>
>
>--
>To unsubscribe, e-mail:   <mailto:taglibs-user-unsubscribe@jakarta.apache.org>
>For additional commands, e-mail: <mailto:taglibs-user-help@jakarta.apache.org>
>
>  
>



--
To unsubscribe, e-mail:   <mailto:taglibs-user-unsubscribe@jakarta.apache.org>
For additional commands, e-mail: <mailto:taglibs-user-help@jakarta.apache.org>


Mime
View raw message