From: raggi <jftucker@gmail.com>
To: rack-devel@googlegroups.com
Cc: ruby-talk@ruby-lang.org, rack-core@googlegroups.com
Subject: Re: [SEC][ANN] Rack 1.5.0, a modular Ruby webserver interface
Date: Mon, 21 Jan 2013 23:46:52 -0800 (PST) [thread overview]
Message-ID: <b986b236-c138-4e2c-b3e0-f1eb1b68d984@googlegroups.com> (raw)
In-Reply-To: <50fe43c2.68dc440a.126d.ffffe987@mx.google.com>
[-- Attachment #1: Type: text/plain, Size: 3528 bytes --]
My sincerest apologies, this was not a SEC release.
On Monday, January 21, 2013 11:46:10 PM UTC-8, raggi wrote:
>
> Hello,
>
> Today we are proud to announce the release of Rack 1.5.0.
>
> = Rack, a modular Ruby webserver interface
>
> Rack provides a minimal, modular and adaptable interface for developing
> web applications in Ruby. By wrapping HTTP requests and responses in the
> simplest way possible, it unifies and distills the API for web servers, web
> frameworks, and software in between (the so-called middleware) into a
> single method call.
> The exact details of this are described in the Rack specification, which
> all Rack applications should conform to.
>
> == Changes
>
> Please note that this release includes a few potentially breaking changes.
> Of particular note are:
>
> * SessionHash is no longer a Hash sublcass
> * Rack::File cache_control parameter is removed in place of headers
> options
>
> Additonally, SPEC has been updated in several areas and is now at 1,2.
>
> A new SPEC section was introduced that provides two server-optional IO
> hijacking
> APIs. Further information on these APIs will be made available by the
> community
> in good time. In the mean time, some information can be found in the
> original
> pull request: https://github.com/rack/rack/pull/481
>
> * January 21st, 2013: Thirty third public release 1.5.0
> * Introduced hijack SPEC, for before-response and after-response
> hijacking
> * SessionHash is no longer a Hash subclass
> * Rack::File cache_control parameter is removed, in place of headers
> options
> * Rack::Auth::AbstractRequest#scheme now yields strings, not symbols
> * Rack::Utils cookie functions now format expires in RFC 2822 format
> * Rack::File now has a default mime type
> * rackup -b 'run Rack::File.new(".")', option provides command line
> configs
> * Rack::Deflater will no longer double encode bodies
> * Rack::Mime#match? provides convenience for Accept header matching
> * Rack::Utils#q_values provides splitting for Accept headers
> * Rack::Utils#best_q_match provides a helper for Accept headers
> * Rack::Handler.pick provides convenience for finding available servers
> * Puma added to the list of default servers (preferred over Webrick)
> * Various middleware now correctly close body when replacing it
> * Rack::Request#params is no longer persistent with only GET params
> * Rack::Request#update_param and #delete_param provide persistent
> operations
> * Rack::Request#trusted_proxy? now returns true for local unix sockets
> * Rack::Response no longer forces Content-Types
> * Rack::Sendfile provides local mapping configuration options
> * Rack::Utils#rfc2109 provides old netscape style time output
> * Updated HTTP status codes
> * Ruby 1.8.6 likely no longer passes tests, and is no longer fully
> supported
>
> == Where can I get it?
>
> You can download Rack at
> http://chneukirchen.org/releases/rack-1.5.0.tar.gz (upload
> pending at time of writing)
> http://rubyforge.org/projects/rack
>
> Alternatively, you can checkout from the development repository with:
> git clone git://github.com/rack/rack.git
> cd rack && git checkout rack-1.5 # for this release
>
> Happy hacking and have a nice day,
>
> James Tucker
> on behalf of the Rack Core Team.
>
> 9f506c84a6edbeb8c98f381e8edce15e7ae08324 rack-1.5.0.tar.gz
> 71b6627efbc8795bd3077eff9850fcb508d57ea3 rack-1.5.0.gem
>
[-- Attachment #2: Type: text/html, Size: 4246 bytes --]
next prev parent reply other threads:[~2013-01-22 7:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-22 7:46 [SEC][ANN] Rack 1.5.0, a modular Ruby webserver interface jftucker
2013-01-22 7:46 ` raggi [this message]
2013-01-22 10:08 ` Eric Wong
2013-01-23 0:27 ` Eric Wong
2013-01-23 22:40 ` Hongli Lai
2013-01-26 19:11 ` James Tucker
2013-01-22 18:14 ` Hongli Lai
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-list from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://groups.google.com/group/rack-devel
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=b986b236-c138-4e2c-b3e0-f1eb1b68d984@googlegroups.com \
--to=rack-devel@googlegroups.com \
--cc=rack-core@googlegroups.com \
--cc=ruby-talk@ruby-lang.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).