On 08 Dec 2010, at 10:48, Lukas Renggli wrote:

> Very cool framework, I like it a lot! I definitely vote to eventually
> replace HTTPSocket with Zinc HTTP Components.

Thanks a lot, I am glad you like it.

> I wonder why ZnFixedClient is not a subclass of ZnHttpClient?

Well, ZnFixedClient is what I wrote earlier for my needs (I use it inside a 
T3RestJsonClient, then T3CachingRestJsonClient and finally a business specific 
T3Client, works very well). ZnHttpClient is Matt's later version, partially 
inspired by your idea of a builder-style API.

> I think it would be cool to be able to use them polymorphic.

We could maybe use some refactoring, consolidation, redesign (hint, hint). But 
for me, it is also a search for good solutions where I don't think that one 
size will fit all, but I could be wrong (for example, Matt's redirection, 
cookie and more advanced authoritzation support would be nice to have 
everywhere, it is just that I did not need it yet in my applications).

Sven



Reply via email to