Return-Path: Delivered-To: apmail-jakarta-commons-httpclient-dev-archive@www.apache.org Received: (qmail 93007 invoked from network); 22 Sep 2003 09:47:48 -0000 Received: from daedalus.apache.org (HELO mail.apache.org) (208.185.179.12) by minotaur-2.apache.org with SMTP; 22 Sep 2003 09:47:48 -0000 Received: (qmail 41252 invoked by uid 500); 22 Sep 2003 09:47:21 -0000 Delivered-To: apmail-jakarta-commons-httpclient-dev-archive@jakarta.apache.org Received: (qmail 41231 invoked by uid 500); 22 Sep 2003 09:47:20 -0000 Mailing-List: contact commons-httpclient-dev-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Commons HttpClient Project" Reply-To: "Commons HttpClient Project" Delivered-To: mailing list commons-httpclient-dev@jakarta.apache.org Received: (qmail 41211 invoked from network); 22 Sep 2003 09:47:20 -0000 Received: from unknown (HELO KCCXOEX11.corp.kpmgconsulting.com) (57.80.136.23) by daedalus.apache.org with SMTP; 22 Sep 2003 09:47:20 -0000 Received: from kccxoex06.corp.kpmgconsulting.com ([10.98.3.31]) by KCCXOEX11.corp.kpmgconsulting.com with Microsoft SMTPSVC(5.0.2195.5329); Mon, 22 Sep 2003 09:44:09 +0000 x-mimeole: Produced By Microsoft Exchange V6.0.6249.0 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Subject: RE: doubt on HttpClient design regarding HttpMethod Date: Mon, 22 Sep 2003 10:47:32 +0100 Message-ID: <825BF35A92B3F0479CC164ECBBE9376E0DE613@kccxoex06.corp.kpmgconsulting.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: doubt on HttpClient design regarding HttpMethod Thread-Index: AcOA7IScgqHNpqEmQIOsL5w6l8o2dwAAWrYQ From: "Kalnichevski, Oleg" To: "Commons HttpClient Project" X-OriginalArrivalTime: 22 Sep 2003 09:44:09.0687 (UTC) FILETIME=[12770E70:01C380EE] X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N Tarun, >From what I know of HttpClient's historical background the project = started as a spin-off of a bigger one. Many design decisions that were = perfectly OK for a bare-minimum library with a limited scope turned out = quite constraining once HttpClient started to evolve into a = comprehensive general-purpose HTTP toolkit. The first generation of = HttpClient developers is long gone already and we can only guess as to = why certain things have been designed the way they are today.=20 We are perfectly aware of many shortcomings of the existing design = (including this one) and are planning to embark on a complete API = overhaul right after 2.1 release. HttpMethod interface split into = HttpRequest/HttpResponse pair is the very first item on our to-do list Regards, Oleg -----Original Message----- From: Elankath, Tarun (Cognizant) [mailto:ETarun@blr.cognizant.com] Sent: Monday, September 22, 2003 11:33 AM To: commons-httpclient-dev@jakarta.apache.org Subject: doubt on HttpClient design regarding HttpMethod Hi all, I am new to HttpClient and was reading through its "Getting started" = section. What struck me immediately is that HttpMethods are full-fledged = objects of their own in HttpClient. I think this is a great idea. However, I don't understand why HttpClient couldn't have something like = a HttpResponse object that is returned when execute() is called. It just = seems a bit kludgy to call getResponse() on the HttpMethod object = itself. Was there a design reason on why this was done ? PLUS: I am enjoying this library. Thank you for it! Regards, Tarun --------------------------------------------------------------------- To unsubscribe, e-mail: commons-httpclient-dev-unsubscribe@jakarta.apache.org For additional commands, e-mail: commons-httpclient-dev-help@jakarta.apache.org