Release 2012.12.08

[Yorick Peterse]

Ramaze 2012.12.08 has just been released after being delayed for several
months. As mentioned in the previous release announcement this release
is **not** backwards compatible. Because of this it is recommended to
carefully read this Email as well as the upgrade notes which can be
found here: http://ramaze.net/documentation/file.upgrading.html.

This new version can be installed as following:

$ gem install ramaze

or:

$ gem install ramaze -v 2012.12.08

## Changelog

* Bug fix for the Sequel cache that would cause it to store session data
for all users.
* Ramaze::Cache is now app-aware instead of always using "pristine" for
the unique identifier. See commit
edabd3c9a476854b72fe2caaa60b25d6c6e60aff
for more information.
* A bug in generate_mapping has been fixed, this bug would cause it to
sometimes incorrectly map URLs and controllers.
* Session IDs are re-generated when logging a user out using the User
helper.
* After uploading a file using the file helper the file handle is
closed instead of leaving the file as is.
* Big performance increase due to changes in Innate (more on this
below).
* Escaping of % sequences when using the Syslog logger.
* Lots of old code such as helpers, loggers and snippets have been
removed (see the upgrade notes for the specific details).
* Various documentation changes such as spelling errors and formatting.
* CSRF tokens no longer expire until the session is destroyed, this
makes it possible to use the same session in multiple browser
windows/tabs.
* Various changes for Ramaze developers to make it easier to develop and
release new versions of Ramaze.

## Compatibility

As mentioned in this Email and the previous release announcement this
version is **not** backwards compatible. A while ago Michael introduced
a change in Innate that speeds it up tremendously by caching various
parts of Innate that don't change during runtime. This change however
meant some code had to be removed, this in turn gave us a chance to
change a few things in Ramaze/Innate in terms of how it handles
middleware.

For those who want to upgrade to this new version I strongly recommend
you to read the upgrade notes mentioned above. These notes explain what
has been removed and how to change your code so that it works with the
new version of Ramaze.

If you happen to bump into any issues or are simply confused feel free
to open an issue on the Github issue tracker or pop in #ramaze on
Freenode.

Yorick

[kez]

Very excited about this release!  Are there any representative benchmarks showing change in overall render times?

Thanks for your continued work in to Ramaze, Yorick!

[Yorick Peterse]

Kez,

A rather crude benchmark (both the code and results) can be found here:

https://gist.github.com/4261993

Yorick

[Michel Blanc]

Wow. While this is JustABenchmark(tm), the numbers are impressive.

Wonderful job, many thanks Yorick & Manveru.

M
--
Michel Blanc - netWorks
8A68 0871 747A 65B6 E87C 3BEA 187C 36BB 2CE5 68BD

[kez]

Rekindling this as the most relevant place to ask my question...

Could you give me a code snippet which will give me source reloading
back in to the run/middleware block? It seems to have been removed
from the default.

Cheers,

kez


On Dec 8 2012, 6:42 pm, Yorick Peterse <yorickpete...@gmail.com>
wrote:

[Yorick Peterse]

Kez,

The reloader still exists in the middleware list for the "dev"
environment (see
https://github.com/Ramaze/ramaze/blob/master/lib/ramaze/default_middleware.rb#L10).
However, we've been getting some reports about some parts of Ramaze not
working as expected so there's a chance something is preventing the
reloader from working properly.

Yorick