Esteban, On 30 May 2012, at 20:25, Esteban A. Maringolo wrote:
> Sven, > > First of all congratulation for your work. It is really good. Thx. > Having ported Swazoo to Dolphin I can figure what it takes to create a whole > new HTTP server/client, so again, kudos to you. > > Regarding the docs, I would switch the links, leaving the no-js option as > the default. That will avoid having to cancel the request and reading there > is an issue with Chrome. Here it doesn't work neither in Chrome nor Chrome > Canary (Win 7 Pro). > > I look forward to start developing in Pharo again for personal pet-projects, > meanwhile I still earn my wage by working with Dolphin, and lately building > HTTP API's on it with Swazoo. > > One of the things that got my attention was how/why you implemented the > ServerDelegates. I would really appreciatie if you want to share with me/us > what was the rationale behind them in comparison with the "alternative" > SwazooResources. Pros and cons, and so on. > > I found the SwazooResources pretty neat to work with, even to implement > special lookups by double dispatching through the URIResolution class. > > Best regards, > > -- > Esteban I did not really think a lot about it: I choose the simplest concept that could work. I guess, from the name and a quick google, that SwazooResource also implies dispatching/routing ? I wanted to avoid that, hence the choice for the delegate concept. I think that something along the lines of SwazooResources could be implemented as a delegate, an extension to Zn. Regards, Sven -- Sven Van Caekenberghe http://stfx.eu Smalltalk is the Red Pill
