DO NOT REPLY [Bug 27589] - MultiThreadedConnectionManager should provide a shutdown
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=27589. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=27589 MultiThreadedConnectionManager should provide a shutdown --- Additional Comments From [EMAIL PROTECTED] 2004-03-29 09:27 --- Thanks. It seems that the nightly builds are done on the HEAD only, so I guess I have to retrieve the source from CVS and build myself. Or is there any plan to have nightly builds for 2.0 support also? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[VOTE][PROPOSAL][RESULT] Promote HttpClient to Jakarta Level
The vote has passed. We will put forth the proposal below to the Jakarta PMC to move HttpClient to a Jakarta level project. The vote details are below: +1 votes - Adrian Sutton [EMAIL PROTECTED] Oleg Kalnichevski [EMAIL PROTECTED] Michael Becke [EMAIL PROTECTED] dIon Gillard [EMAIL PROTECTED] +0 votes - Ortwin Glück [EMAIL PROTECTED] Vote thread - http://nagoya.apache.org/eyebrowse/BrowseList?listName=commons-httpclient-de [EMAIL PROTECTED]by=threadfrom=681919 (0) RATIONALE HTTP is the main protocol used today on the internet. Although the JDK includes basic support for building HTTP-aware client applications, it doesn't provide the flexibility or ease of use needed for many projects. The current package in Jakarta-Commons is a widely used implementation with a strong community behind it. The size of it's community and it's project has significantly outgrown the commons project and a move to a Jakarta level project would provide better support for that community and for the on going development of HttpClient. (1) SCOPE The project shall create and maintain a Java library implementing the client side of the HTTP 1.0 and 1.1 protocol, as defined in RFC 1945, RFC 2616 and RFC 2617. HttpClient also supports the following RFCs. * RFC 2109 for HTTP state management mechanism (Cookies) - an upgrade to RFC 2965 is planned for a future version of HttpClient * RFC 2396 Uniform Resoruce Identifiers (URI): Generic Syntax * RFC 1867 Form-based File Upload in HTML The package should: * Have an API which should be as simple to use as possible * Be as easy to extend as possible * Provide unconditional support for HTTP/1.1 The package is quite different from the HTTP client provided as part of the JDK (java.net.HttpURLConnection), as it focuses on the HTTP methods being sent (instead of making that transparent to the user), and generally allows more interaction with the lower level connection. The JDK client is also not very intuitive to use. The package is used by a wide range of projects both within the ASF and from third parties. These include: * Jakarta Slide * Jakarta Commons Latka * Nortel Networks * HtmlUnit * Jakarta Cactus * JSR 147 * NOSE Applied Intelligence ag * MindIQ's Design-a-Course * ContactOffice * Newknow * de4d2c * Furies * Term Highlighting for Verity Ultraseek search results * Mule - Universal Message Objects * many more. (1.5) Interaction With Other Packages HttpClient relies on: * Java Development Kit (Version 1.2 or later; 1.3 or later recommended) * Jakarta commons-logging (Version 1.0 or later) * Jakarta commons-codec (Version 1.2 or later) (2) INITIAL SOURCE OF THE PACKAGE The initial codebase exists as a sub-project of Jakarta-Commons, in the httpclient subdirectory of the jakarta-commons cvs tree. The proposed package name for the new sub-project is org.apache.httpclient. (3) REQUIRED JAKARTA RESOURCES * CVS Repository - New module, jakarta-httpclient in the CVS repository. * Initial Committers - The list is provided below. All of the proposed committers are currently jakarta-commons committers. * Mailing List - Two new mailing lists will be required: [EMAIL PROTECTED] and [EMAIL PROTECTED] These will be used for developer discussions and user discussions respectively. CVS commit messages will be sent to the httpclient-dev list. * Bugzilla - New product category HttpClient, with appropriate version identifiers as needed. Existing bugs in the HttpClient component under the Commons product category will need to be migrated. (4) INITIAL COMMITTERS The initial committers on the HttpClient component shall be: * Michael Becke * Jeff Dever * dIon Gillard * Ortwin Glück * Oleg Kalnichevski * Adrian Sutton Adrian Sutton -- Intencha tomorrow's technology today Ph: 38478913 0422236329 Suite 8/29 Oatland Crescent Holland Park West 4121 Australia QLD www.intencha.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: DO NOT REPLY [Bug 27589] - MultiThreadedConnectionManager should provide a shutdown
Yes, unfortunately the nightly builds are from HEAD. I'm not sure if we can create both 2.0 and HEAD nightly builds. Anyone know more about this? Mike On Mar 29, 2004, at 4:27 AM, [EMAIL PROTECTED] wrote: 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=27589. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=27589 MultiThreadedConnectionManager should provide a shutdown --- Additional Comments From [EMAIL PROTECTED] 2004-03-29 09:27 --- Thanks. It seems that the nightly builds are done on the HEAD only, so I guess I have to retrieve the source from CVS and build myself. Or is there any plan to have nightly builds for 2.0 support also? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: DO NOT REPLY [Bug 27589] - MultiThreadedConnectionManager should provide a shutdown
Mike, I believe the only way to find this out is to approach the infrastructure folks ([EMAIL PROTECTED]) Oleg On Mon, 2004-03-29 at 15:30, Michael Becke wrote: Yes, unfortunately the nightly builds are from HEAD. I'm not sure if we can create both 2.0 and HEAD nightly builds. Anyone know more about this? Mike On Mar 29, 2004, at 4:27 AM, [EMAIL PROTECTED] wrote: 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=27589. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=27589 MultiThreadedConnectionManager should provide a shutdown --- Additional Comments From [EMAIL PROTECTED] 2004-03-29 09:27 --- Thanks. It seems that the nightly builds are done on the HEAD only, so I guess I have to retrieve the source from CVS and build myself. Or is there any plan to have nightly builds for 2.0 support also? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE][PROPOSAL][RESULT] Promote HttpClient to Jakarta Level
On 29/3/04 8:47 PM, Adrian Sutton [EMAIL PROTECTED] wrote: The vote has passed. We will put forth the proposal below to the Jakarta PMC to move HttpClient to a Jakarta level project. The vote details are below: I also want to note that I've received replies from Rodney Waldhoff and Sung-Gu. Rodney wants to retain his emeritus committer status but doesn't currently have time to contribute to HttpClient - I assurred him that he can return to full active committer status at any stage. Sung-Gu is keen to rejoin the ranks of active HttpClient committers and apparently is faxing through his CLA at which point we will likely hear from him on this list. Regards, Adrian Sutton -- Intencha tomorrow's technology today Ph: 38478913 0422236329 Suite 8/29 Oatland Crescent Holland Park West 4121 Australia QLD www.intencha.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: DO NOT REPLY [Bug 27589] - MultiThreadedConnectionManager should provide a shutdown
Message sent. Mike On Mar 29, 2004, at 4:26 PM, Oleg Kalnichevski wrote: Mike, I believe the only way to find this out is to approach the infrastructure folks ([EMAIL PROTECTED]) Oleg On Mon, 2004-03-29 at 15:30, Michael Becke wrote: Yes, unfortunately the nightly builds are from HEAD. I'm not sure if we can create both 2.0 and HEAD nightly builds. Anyone know more about this? Mike On Mar 29, 2004, at 4:27 AM, [EMAIL PROTECTED] wrote: 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=27589. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=27589 MultiThreadedConnectionManager should provide a shutdown --- Additional Comments From [EMAIL PROTECTED] 2004-03-29 09:27 --- Thanks. It seems that the nightly builds are done on the HEAD only, so I guess I have to retrieve the source from CVS and build myself. Or is there any plan to have nightly builds for 2.0 support also? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
