By default, these classes use Marshal for serializing and deserializing messages. Unfortunately, the Marshal format is closely associated with Ruby internals and even changes between different interpreters. This makes the resulting message very hard to impossible to unserialize messages generated by these classes in other environments like node.js.

This patch solves this by allowing you to set your own custom serializer and deserializer lambda functions. By default, it still uses Marshal to be backwards compatible.

Allow asset tag helper methods to accept :digest => false option in order to completely avoid the digest generation.

Clear cache before of each precompile to avoid inconsistencies. Fixes #3014

Add missing changelog entries for actionpack

Revert "Provide a way to access to assets without using the digest, useful for static files and emails"

This reverts commit 82afaa06.

Silence Ruby warnings about uninitialized instance variable.

Don't mount Sprockets if config.assets.compile is disabled

There is no meaningful performance penalty in defining attribute
methods, since it only happens once.

There is also no reason *not* to define them, since they get thrown in
an included module, so they will not 'overwrite' anything. In fact, this
is desirable, since it allows us to call super.

There's no harm in generating a method name that's already defined on
the host class, since we're generating the attribute methods in a module
that gets included. In fact, this is desirable as it allows the host
class to call super.

We can just use method_defined? and private_method_defined?

For consistency with find_or_initialize_by. Also remove first_or_build
alias.

Fix precompile asset_host test

Fix for relative url root in assets

Move asset tests to assets_test file