> Hi, > > Maybe I am a bit late with this question, I also don't know who makes the > decision, and it is probably external people who have to make the judgement, > but would it be possible and/or a good idea to include Zinc HTTP Components > into Pharo 1.2 Dev ? > > In any case, the code is in good shape, works on 1.2, has a reasonable number > of tests, has comments, is pretty small and elegant. > > Whether or not to load the Zinc-Patch-HTTPSocket package is another question. > This package patches (destructively overwrites) class methods in HTTPSocket, > redirecting them to ZnHTTPSocketFacade, effectively steering all HTTP client > access in your Smalltalk image through Zinc HTTP Components. This has been > working for me for months, but my usage is certainly not universal. So maybe > this should remain an option. > > I would especially like to expose this code to more people to get more > feedback. I am also willing to keep on supporting the code. > > What do you think ?
big +1 I think you're doing a great job. > has a reasonable number of tests, has comments, is pretty small and elegant. totally true to me, but as I'm not an expert nor an intensive user, my impression is just when reading your code and using it a bit. Same impression as XMLSupport ie. some reference packages... So I vote for inclusion :). Killing HTTPSocket class method is also important but as you said it can maybe wait... My 2cents Cédrick > > Sven > > > >
