Comments on: Rack RESTful Dispatcher

By: Peter Cooper

Peter Cooper — Thu, 31 Jan 2008 08:03:59 +0000

Frank: It doesn’t really matter. Ruby just treats strings as series of 8 bit bytes, so you can store an image in a string, or whatever. Piping it out via HTTP via a string will work fine. For example, if you made it use image/gif for the content type, you could easily just send File.read(’whatever.gif’) straight back and it’d work.

By: lucasjosh.com » Blog Archive » Links for 1/30/08 [my NetNewsWire tabs]

Thu, 31 Jan 2008 05:14:16 +0000

[...] Nutrun » Blog Archive » Rack RESTful Dispatcher [...]

By: links for 2008-01-30 | Lazycoder

links for 2008-01-30 | Lazycoder — Wed, 30 Jan 2008 10:26:37 +0000

[...] Nutrun » Blog Archive » Rack RESTful Dispatcher (tags: ruby rack programming) [...]

By: Web 2.0 Announcer

Web 2.0 Announcer — Wed, 30 Jan 2008 10:12:31 +0000

Rack RESTful Dispatcher…

[...]Example of using Rack to create standalone RESTFul services in Ruby.[...]…

By: links for 2008-01-30 « Bloggitation

links for 2008-01-30 « Bloggitation — Wed, 30 Jan 2008 00:21:25 +0000

[...] Rack RESTful Dispatcher (tags: ruby rest web programming web2.0) [...]

By: George Malamidis

George Malamidis — Tue, 29 Jan 2008 14:41:43 +0000

http://rack.rubyforge.org/doc/classes/Rack/File.html

By: Frank Carver

Frank Carver — Tue, 29 Jan 2008 14:33:07 +0000

This looks a lot like the a naive version of Mojasef Java framework which I have been using successfully for several years now.

I’m surprised at the choice of an array of strings for the body type, though. I wonder how that is supposed to handle non-textual responses, such as serving an image, for example.