But do please consider changing the name of the “retreive” function to “retrieve”.

Otherwise you will confuse people forever (like the guy who made the “referer” misspelling a permanent part of the HTTP spec…). I know this is inconsistent with the spelling of “receive”, but that’s an unfixable bug in the English language…

sinatra$ ack session lib/
lib/sinatra/base.rb
106:    # Access the underlying Rack session.
107:    def session
108:      env['rack.session'] ||= {}
921:        builder.use Rack::Session::Cookie if sessions?
999:    set :sessions, false
1063:    set :sessions, false

If Rack is not installed (the gem I mean) then sinatra cannot provide session support. This was my point here.

Sure?

“Sinatra ships with basic support for cookie-based sessions”
http://www.sinatrarb.com/book.html#sessions

Also, “retrieve” is the more common spelling :-)

Not really, since Rack is Rack, and most users would just use Rack. And even if you run in non-Rack with servers, $env['rack.session'] is an abstract interface to get/set objects, so it should be easy (or at least possible) to write a middleware can that sets the env variable that does duck typing.

We actually had that stuff in HTTP::Engine::Middleware, which uses the generic HTTP::Session module:
http://search.cpan.org/~yappo/HTTP-Engine-Middleware-0.17/lib/HTTP/Engine/Middleware/HTTPSession.pm
http://search.cpan.org/~tokuhirom/HTTP-Session-0.32/