RE: HttpClient development

On Mon, 2002-05-06 at 17:43, Donald Ball wrote: > anyway, attached is a short usage sample document for HttpClient. i'll > see about fleshing it out if anyone has any comments. er, okay, looks like jakarta's mail server silently drops attachments. here it is inline. - donald Usage

RE: HttpClient development

I know how it works, and I am willing to put in effort to rectify what's wrong. But my gut feeling, and I've been doing software architecture for years, is that the way the package is done is too complex. For example, how is someone to start a session? HttpClient? HttpMultiClient? URLxxxMethod?

RE: HttpClient development

On Mon, 2002-05-06 at 16:01, [EMAIL PROTECTED] wrote: > Please provide specific examples of *what* you found confusing and *why*. > Better yet, supply patches or documentation that you think make things > better, this is a volunteer effort. a simple document walking through an example program us

cvs commit: jakarta-commons/latka/src/conf latka-webapp-web.xml

morgand 02/05/06 14:43:40 Modified:latka/src/conf latka-webapp-web.xml Log: IO taglib is no longer used - Tomcat 4.1 is more strict about taglib definitions Revision ChangesPath 1.2 +0 -5 jakarta-commons/latka/src/conf/latka-webapp-web.xml Index: latka-

cvs commit: jakarta-commons/logging/src/java/org/apache/commons/logging/impl Jdk14Logger.java Log4JCategoryLog.java

costin 02/05/06 14:32:37 Modified:logging build.xml logging/src/java/org/apache/commons/logging/impl Jdk14Logger.java Log4JCategoryLog.java Log: Few small (?) fixes: - for JDK1.4, include the correct class/method. This uses a hack to e

Re: [Latka] Maven comes, servlets go

The build.xml file for the webapp was also not updated to indicate the revised directory structure. --- Morgan Delagrange <[EMAIL PROTECTED]> wrote: > Hi all, > > The webapp build is broken. dion, the Latka webapp > included two servlets necessary for viewing test > files > and HTTP responses f

[Latka] Maven comes, servlets go

Hi all, The webapp build is broken. dion, the Latka webapp included two servlets necessary for viewing test files and HTTP responses from test runs. It looks like you deleted those servlets and didn't put them somewhere else when you reorganized the source tree. Actually, I'm not quite happy w

RE: HttpClient development

+1 to all of that. Well said Marc. > There are two usage models that I know of: > HttpClient and HttpMultiClient. A third model, and the one I use almost exclusively, is to ignore HttpClient (and HttpMultiClient) altogether and just work with HttpMethod, HttpConnection and HttpState directly.

RE: HttpClient development

Please provide specific examples of *what* you found confusing and *why*. Better yet, supply patches or documentation that you think make things better, this is a volunteer effort. There are two usage models that I know of: HttpClient and HttpMultiClient. HttpClient is the original model and its

RE: HttpClient development

On Mon, 2002-05-06 at 12:52, Amir D. Kolsky wrote: > As a developer new to HttpClient I have to admit to be extremely confused by the package. Several usage models are concurrently impelemented, virtually no documentation exists as to how to do what, and worse, it appears that there is no one at

RE: HttpClient development

I agree with this to certain degree. The presence and HttpClient and HttpMultiClient is extremely confusing to the user. Although HttpMultiClient is what most people really need, most people will take the wrong guess and use HttpClient. Maybe we should just rename HttpMultiClient to HttpClient. An

RE: HttpClient development

I agree that it would be desirable to allow '1 time' setting of certain request headers. I suggested this before and I think I sent some patches, at least for HttpConnection (and maybe HttpClient, I don't remember any more). Otis ___ Sig

Re: [VOTE] [pool] Pool 1.0 Release

+1 --- [EMAIL PROTECTED] wrote: > +1 > > -- > Martin Cooper > > > At 07:20 AM 5/4/2002, Waldhoff, Rodney wrote: > >Please vote on the proposed 1.0 build at > >http://jakarta.apache.org/builds/jakarta-commons/release/commons-pool/v1 > >.0/. > > > > > -- > To unsubscribe, e-mail: >

RE: HttpClient development

Although it's possible to do so on a method base, it makes sense to change the default as well. I reported this bug before and it was marked invalid: http://nagoya.apache.org/bugzilla/show_bug.cgi?id=6627 -Original Message- From: Waldhoff, Rodney [mailto:[EMAIL PROTECTED]] Sent: Monday,

Re: [VOTE] [pool] Pool 1.0 Release

+1 -- Martin Cooper At 07:20 AM 5/4/2002, Waldhoff, Rodney wrote: >Please vote on the proposed 1.0 build at >http://jakarta.apache.org/builds/jakarta-commons/release/commons-pool/v1 >.0/. -- To unsubscribe, e-mail: For additional commands, e-mail:

RE: HttpClient development

Yes, this is the place. Ask away. Scott > -Original Message- > From: Donald Ball [mailto:[EMAIL PROTECTED]] > Sent: Sunday, May 05, 2002 1:07 PM > To: [EMAIL PROTECTED] > Subject: HttpClient development > > > is this the appropriate forum to ask questions about > HttpClient developm

RE: HttpClient development

As a developer new to HttpClient I have to admit to be extremely confused by the package. Several usage models are concurrently impelemented, virtually no documentation exists as to how to do what, and worse, it appears that there is no one at the helm to guide this package in a coherent and ar

RE: jakarta.apache.org/commons/components.html

> How do I go about adding the new[ok old now] > sandbox components to the webpage? Just edit or patch the files in the commons/xdocs directory (http://cvs.apache.org/viewcvs/jakarta-commons/xdocs/). Miminal publish instructions can be found at http://cvs.apache.org/viewcvs/jakarta-commons/BUIL

cvs commit: jakarta-commons-sandbox/resources STATUS.html

dlr 02/05/06 09:30:06 Modified:resources STATUS.html Log: Martin notes that I should be adding my name to _this_ file before doing commits. :-) Revision ChangesPath 1.4 +2 -1 jakarta-commons-sandbox/resources/STATUS.html Index: STATUS.html ==

RE: [pool] 1.0 release soon

>That's not true. AFAIK, every mutable property in >org.apache.commons.pool.impl.* follows the getProperty/setProperty >conventions, and always have. Another important piece of the conventions is that all beans have a zero-arg constructor, which the core pool classes don't have. As I said, it w

RE: [pool] 1.0 release soon

> The classes don't follow the javabean conventions, That's not true. AFAIK, every mutable property in org.apache.commons.pool.impl.* follows the getProperty/setProperty conventions, and always have. > As it's designed now (or as it was a month ago), pool > and DBCP are not very Digester frien

DO NOT REPLY [Bug 8825] New: - createPath without value

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 8823] New: - removal of nodes

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 8822] - createPath does not work for an empty DOM

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 8822] New: - createPath does not work for an empty DOM

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bu

jakarta.apache.org/commons/components.html

How do I go about adding the new[ok old now] sandbox components to the webpage? And what's the policy on which ones get added? We have lots more in the sandbox than are currently on the page. I was hoping to add: io, net, codec and lang. Oh and servlet. Initially just pointing to the sandbox as

RE: [pool] 1.0 release soon

> Are there plans to replace JOCL with Digester for this release ? >We're using DBCP with JOCL for an application which will go to >production soon. And we'd like to know the road-map for moving it to >digester. As it's designed now (or as it was a month ago), pool and DBCP are not very D

RE: HttpClient development

> 3. is there any way to set the User-Agent string for an httpclient? >> Nope, but this has come up before. If there >> isn't one already, add an enhancement request to >> the Bugzilla database so we don't forget. You can do this on a per-method basis: method.setRequestHeader("User-Agent","M

[GUMP] Build Failure - commons-util

This email is autogenerated from the output from: Buildfile: build.xml BUILD FAILED Target `dist' does not exist in this

RE: HttpClient development

> > 3. is there any way to set the User-Agent string for an httpclient? > Nope, but this has come up before. If there isn't > one already, add an enhancement request to the > Bugzilla database so we don't forget. Actually, there is a way on a method-per-method basis. Simply call method.setR