DO NOT REPLY [Bug 11218] - handle multivalue headers correctly

2003-02-10 Thread bugzilla
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=11218. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.

DO NOT REPLY [Bug 11218] - handle multivalue headers correctly

2003-02-09 Thread bugzilla
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=11218. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.

Re: DO NOT REPLY [Bug 11218] - handle multivalue headers correctly

2003-02-07 Thread Michael Becke
There has not been any more discussion about this since my last response. Does anyone else have comments? If not, Jeff please let me know how you want me to proceed on this. Thanks, Mike On Tuesday, February 4, 2003, at 08:53 AM, Michael Becke wrote: - no need for fully qualified class

Re: DO NOT REPLY [Bug 11218] - handle multivalue headers correctly

2003-02-07 Thread Jeffrey Dever
I've been thinking about it too. I still feel that we should keep the HeaderGroup behind the scenes, and only expose Header[]. This will still solve the requirements of this feature, while protecting users from change. We can consider making HeaderGroup public in 2.1. Ideally we could add

Re: DO NOT REPLY [Bug 11218] - handle multivalue headers correctly

2003-02-04 Thread Michael Becke
- no need for fully qualified class names in @see or @link comments - please use @since 2.0beta1 new methods/classes Can do. - don't see a need for getFirstHeader and getLastHeader I didn't think so at first either. For some uses though I think it works. For example if you want to get the

DO NOT REPLY [Bug 11218] - handle multivalue headers correctly

2003-02-03 Thread bugzilla
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=11218. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.

Re: DO NOT REPLY [Bug 11218] - handle multivalue headers correctly

2003-02-03 Thread Jeffrey Dever
- no need for fully qualified class names in @see or @link comments - please use @since 2.0beta1 new methods/classes - don't see a need for getFirstHeader and getLastHeader - getCondensedHeader, if there is one header, it returns a refrence to an internal datastructure, if more than one, it

DO NOT REPLY [Bug 11218] - handle multivalue headers correctly

2003-01-26 Thread bugzilla
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=11218. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.