On Jan 7, 2011, at 2:02 PM, Adrian Lienhard wrote: > Hi Sven, > > +1 for Pharo 1.2 (the dev image) > -1 for patching HTTPSocket (dev packages should not modify core code) > > For 1.3 we should think about integrating Zinc in PharoCore to replace > HTTPSocket.
Yes! > > Cheers, > Adrian > > > On Jan 7, 2011, at 11:05 , Sven Van Caekenberghe wrote: > >> 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 ? >> >> Sven >> >> >> >> > >
