I'm currently reading _The Pragmatic Programmer_, and I just came across the
following in a section entitled Comments in Code on page 250:
One of the most important pieces of information that should appear in the
source file is the author's name -- not necessarily who edited the file
last, but
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=27594.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
That's exactly the problem:
not necessarily who edited the file last, but the owner
There are people who see a chance to contribute an
enhancement or bug fix. We'd like to have them listed
as someone who contributed, but *without* the
responsibility of being the owner of the code.
cheers,
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=27594.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=27594.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=22655.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=27594.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=22655.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
Except for error handling and stuff, this is the right approach.
To store the image, you have to create a FileOutputStream
and copy the response data there. See also the section
Read the Response in the tutorial:
http://jakarta.apache.org/commons/httpclient/tutorial.html
cheers,
Roland
The last time I have try to used HttpClient with JBoss, I have occur many
problem (I hope your remeber, about 3 month ago). I have try to look where
the probleme is, but I was not able to find :(
So, if HttpClient is bundled with JBoss, I will be volontair for testing
again. (And it is). I will
Thanks, Jean-Marc.
Keep us posted about the results of your tests
Oleg
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: Thursday, March 11, 2004 14:33
To: Commons HttpClient Project
Subject: Re: HttpClient in JBoss
I confirm.
JBoss is using HttpClient in
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=26070.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=27594.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
Very nice quote. But the owner of HttpClient (and all jakarta project
code) is *very* clear. The owner is the Apache Software Foundation
(ASF). The individual contributor has contributed the code, and does
need to be recognized, but when a commit is made that code no longer
belongs to them.
I think that owner is intended in the sense of the primary person
responsible for maintaining, not in the sense of the legel owner.
The programmer is only very rarely the legal owner of his work.
Jeff Dever wrote:
Very nice quote. But the owner of HttpClient (and all jakarta project
code) is
Dan Christopherson wrote:
I think that owner is intended in the sense of the primary person
responsible for maintaining, not in the sense of the legel owner.
Honestly, there is no such thing in this project. The responsible
persons are the (few) active committers. Those change (slowly) over
The tags clearly are not ownership oriented. That is why they have dates
and what was done.
At 01:29 AM 3/11/2004, you wrote:
That's exactly the problem:
not necessarily who edited the file last, but the owner
There are people who see a chance to contribute an
enhancement or bug fix. We'd like
Can someone tell me in a word or two WHY this change is important? What is
the problem that needs to be fixed?
At 07:03 AM 3/11/2004, you wrote:
Very nice quote. But the owner of HttpClient (and all jakarta project
code) is *very* clear. The owner is the Apache Software Foundation
(ASF).
Bravo, author of code and especially code parts does not mean owner in
any sense. Author means author, which is accurate.
At 09:07 AM 3/11/2004, you wrote:
I think that owner is intended in the sense of the primary person
responsible for maintaining, not in the sense of the legel owner.
The
Fair point. ASF is the legal owner, not the maintainer. But @author
tags do not help in identifying the maintainer at all for many reasons.
A maintainer really implies one place or person for contact. A running
list of @author tags, some current some ancient, do not satisfy this.
The only
I'm not on the board, but I'm aware of two issues:
1) The ASF board has concerns over the legal ramifications of @author
tags in code. IE it might be possible for someone to sue someone listed
as an @author.
2) The tags have caused social issues in some projects (conflicts
between people) which
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=27434.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
On the first issue, I am a lawyer and I can assure you that this worry is,
frankly, silly. Unless you are going to hide who did coding, then this is
also completely ineffective to meet that worry, which, as I said, is silly
anyway.
The second issue cannot be commented on because what the
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=26070.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
Hi Adrian, I hadn't heard about the problem in 1.4.2. Do you have any other
information about it?
Bruce.
-Original Message-
From: Adrian Sutton [mailto:[EMAIL PROTECTED]
Sent: Tuesday, March 09, 2004 5:14 PM
To: Commons HttpClient Project
Subject: Re: Proxy detection in the Sun plugin
On 12/3/04 7:34 AM, Bruce McHaffie [EMAIL PROTECTED] wrote:
Hi Adrian, I hadn't heard about the problem in 1.4.2. Do you have any other
information about it?
I don't at the moment unfortunately. It may be that I'm the only person
seeing it for all I know right now. We haven't received any
Hi All,
Quick simple question -- does anyone recall if any bugs related to
HTTP Proxies were fixed between RC2 and the final release? We're using
a customized version of RC2 right now and are planning to start making
use of the proxies. If any problems were discovered, I can re-sync our
Hi Sam,
I recall working on a pretty nasty bug related to NTLM host/proxy
authentication past the RC2 release
The tagging convention is:
HTTPCLIENT_major-version_minor-version_release
2.0rc2 has been tagged as HTTPCLIENT_2_0_RC2
2.0 (final) has been tagged as HTTPCLIENT_2_0_FINAL
Oleg
On Thu,
The vote to promote HttpClient passed with 4 +1s and 2 +0s.
We will now need to work on a proposal and start talking with the PMC
about working on the logistics. Jeff, now that you have returned
(welcome back, it's good to hear from you again) would you like to
start the dialogue with the
Hey Mike,
Sure, I'd be happy to do that. I'll start with it just after the
@author discussion cools down (its hot right now) and the Sung-Gu/Sean
issue gets resolved. You should also read and follow these guidelines
when preparing the proposal:
http://jakarta.apache.org/site/newproject.html
30 matches
Mail list logo
