On Thu, 2007-01-25 at 23:43 +0100, Stojce Dimski wrote: > Hi Oleg, > > Does this mean that you are suggesting to do away with HttpParams > > interface entirely? If not, what would be the way to bridge the > > suggested framework and HttpCore which currently relies on HttpParams? > Yes I am suggesting exactly that... If we use a simple beans, with > getters and setters spring and other frameworks fits like a glove, > because the beans are their "bread and butter" and everything is dead > simple... Also using this approach we can make some sensible default > values and get "convention over configuration"... Just imagine all > examples without even one line of "params.setParameter"... >
Stojce, The existing preferences API based HttpParams [1] was developed in HttpClient 3.x for a good reason. It allows for a great deal of flexibility and enables the users to introduce custom parameters without having to change anything in the stock version of HttpClient. I am skeptical that plain old java beans could replace it. Having said that I am open to alternatives and will be happy to review patches Oleg [1] http://jakarta.apache.org/commons/httpclient/preference-api.html > Thanks, > Stojce > > > --------------------------------------------------------------------- > 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]
