Excerpts from Sven Van Caekenberghe's message of 2015-01-30 07:53:46 +0100: > > This microframework is quite handy for REST API (and the README of the repo > > is *really* useful) > > http://smalltalkhub.com/#!/~zeroflag/Teapot > So many options, there is Zinc-REST as well...
i am aware of both. i want to take a look at Zinc-REST first though. i looked at Teapot briefly. i am not a fan of routing all urls from a central location , i prefer a way where i delegate a namespace say "/people" where a class then is responsible for what happens within that namespace. iaw: if i go to "/people/person/2" then the HandlePeople class would be called with the argument "person/2" or even #(person 2) this allows me to map a REST api to an arbitrary object hierarchy, where the base urls are only defined by the hierarchy which itself is not even aware of REST, and once the object is located i only need to connect the REST interaction to it and have it work the same way regardless of where in the hierarchy that object actually lives. greetings, martin. -- eKita - the online platform for your entire academic life -- chief engineer eKita.co pike programmer pike.lysator.liu.se caudium.net societyserver.org secretary beijinglug.org mentor fossasia.org foresight developer foresightlinux.org realss.com unix sysadmin Martin Bähr working in china http://societyserver.org/mbaehr/
