Sven Van Caekenberghe wrote > > Now that I have recovered from the intensive Pharo Conference, I found the > time to publish the Zinc and Zodiac documentation. > ... > http://zn.stfx.eu/zn/zinc-http-components-paper.html > http://zdc.stfx.eu/zodiac-paper.html >
Wow, really clear and thorough. The way the raw internet protocols are woven into the examples is really cool (I always have to be reminded that there's no magic, just binary turtles all the way down)... And I found numberOfRetries:, retryDelay:, contentReader:, and #enforceHttpSuccess: particularly useful in simplifying my code A few thoughts: * ZnClient>>retryDelay: - it'd be nice if it took aDuration. If I was reading someone else's code, "client retryDelay: 30" forces me to find the method, but "client retryDelay: 30 seconds" is clear - I think it should return self, like enforceHttpSuccess:. Besides consistency, it will avoid having to send #yourself when configuring a new client instance. * JSJsonParser - where does this class live? A reference would be great... * FileSystem - I remember you mentioned having a problem with FS. Has this been solved? There is a slice in the inbox which replaces all uases of FileDirectory and friends with FS. Also, how will this effect portability (e.g. to Squeak). If you make Zn depend on FS, is the Pharo (renamed classes) version of FS loadable in Squeak trunk? * [up/down]load convenience methods - What do you think about adding e.g. ZnEasy>>download:to: & upload:to: (is POST a good default?) -- View this message in context: http://forum.world.st/Zinc-Zodiac-Documentation-tp4632114p4632508.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.
