Am 12.02.2013 um 13:51 schrieb Frank Shearar <frank.shearar at gmail.com>:

> On 9 January 2013 20:54, Chris Muller <asqueaker at gmail.com> wrote:
>> The best way is to test it is on your own machine.  Do you have access
>> to the server?
>> 
>> In /home/squeakmap is the server image -- Squeak3.8-6665-sm.image.
>> Grab it and the changes as well as  "start.st" boots the server in the
>> same directory (note a classic VM is required).  Running it on your
>> localhost so can actually step through debugger in the server to make
>> sure the change works.
>> 
>> This is how I did the 2011 enhancements for the Release Editor and CSP
>> improvements.
>> 
>> Doing this will also bring to light how badly we really need to
>> improve or replace SqueakMap's implementation, particularly on the
>> server side.  :(   The domain model itself is actually pretty nice,
>> but the machinery needs improvement.
> 
> I poked around a fair bit and can't figure out how anything actually
> gets done. What would be really great is something somewhere saying
> "these are the routes we accept, that define the API as HTTP sees it"
> and that delegates implementation thereof to other objects. Kind've
> what one would see in a Sinatra app, I guess:
> https://github.com/lshift/rabbitmq-service-sinatra-sample/blob/master/rabbit.rb
> 

Tim Felgentreff has done RatPack, a sinatra-like mini-framework on top of Kom
https://github.com/timfel/ratpack

Best
	-Tobias