On Fri, 2007-01-26 at 12:38 +0100, Stojce Dimski wrote: > Ok guys, I thought about this question little more... > > As changes to HttpParams impact nearly every part of the framework, > maybe for now is better to leave it as it is, and maybe later, refactor > it... Pity as major version release is a best moment to change something...
Stojce, HttpCore is still ALPHA and we are still in the position to make significant API changes, but we ought not do this without a very good reason. Here's my suggestion. Please go ahead and create a new preferences framework based on plain old java beans, get it to work with Spring, and then hack up a quick and dirty converter from the new API to HttpParams API. If we all find the new API capable of completely replacing HttpParams, we can still decide to bite the bullet, move HttpCore to the new API and help existing users adapt their applications. If not, the new API will just stay in the optional Spring module and we'll have to invest some efforts into improving the bridge between the two APIs. Does this make sense? Oleg > Next week I will see to implement something called > 'HttpParamsFactoryBean' which will be the bean which is BasicHttpParams > and which load his parameters from external .properties file... With > this we get rid of parameter setting in source code and finaly > externalise the configuration... If I have enough time will look into > custom schema support also... > > 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]
