Commits
-------

a3885545 Fix JSON recipe, fixes #419

Discussion
----------

Fix JSON recipe, fixes #419

Commits
-------

197d2400 Fix PHP 5.4 built-in webserver front controller

Discussion
----------

Fix PHP 5.4 built-in webserver front controller

The problem is that with `php -S localhost:8080 -t web` it will only route
one level of paths to index.php. This is stupid, but requires us to use
a router script, which means that we must specify `index.php` and have
that script return false when the web server should serve from disk.

Thanks to @schokocappucino for the hints.

Commits
-------

bcbd71ec Add minimum-stability flag to all composer.json samples

Discussion
----------

Add minimum-stability flag to all composer.json samples

Today marks the release of composer alpha4. This changes the default
stability from dev to stable, which means that if you want to use un-
stable dependencies, you either have to specify a root package level
minimum-stability, or use the @dev constraint, i.e. "1.0.*@dev".

We are setting the minimum-stability, so that we do not have to use
@dev for all dependencies, and all dependencies of dependencies.

We can increase the stability to beta once we release a beta of silex
(this will use Symfony 2.1 beta releases), and when we make a final
release (some time after Symfony 2.1.0), the flag can be removed.

Today marks the release of composer alpha4. This changes the default
stability from dev to stable, which means that if you want to use un-
stable dependencies, you either have to specify a root package level
minimum-stability, or use the @dev constraint, i.e. "1.0.*@dev".

We are setting the minimum-stability, so that we do not have to use
@dev for all dependencies, and all dependencies of dependencies.

We can increase the stability to beta once we release a beta of silex
(this will use Symfony 2.1 beta releases), and when we make a final
release (some time after Symfony 2.1.0), the flag can be removed.

The problem is that with `php -S localhost:8080 -t web` it will only route
one level of paths to index.php. This is stupid, but requires us to use
a router script, which means that we must specify `index.php` and have
that script return false when the web server should serve from disk.

Funny part: We are almost lying now, because the webserver now requires
some sort of configuration (via code), but I will leave it in the docs
for marketing reasons. It's not a big lie after all.

Commits
-------

fff4314e Add note about the PHP 5.4 webserver to webserver docs

Discussion
----------

Add note about the PHP 5.4 webserver to webserver docs

Commits
-------

9a5692cf Fixed Lighttpd's configuration indent level

Discussion
----------

Fixed Lighttpd's configuration indent level

Commits
-------

8cf66cbc Improve validator provider doc

Discussion
----------

Improve validator provider doc

Add a small note and fix rst syntax of this page : http://silex.sensiolabs.org/doc/providers/validator.html#validating-arrays

removed the auto-starting of the session when a previous session exists as the session is now always auto-started

Commits
-------

b4f7ce21 Fixed typo
cb3fd7d5 Changed in phpunit.xml.dist and added testsfor lazy url matcher

Discussion
----------

Changed in phpunit.xml.dist and added testsfor lazy url matcher

* Changed in phpunit.xml.dist make sure that tests will covers only code in src directory.
* Added lazy url matcher

Tests passed: [![Build Status](https://secure.travis-ci.org/l3l0/Silex.png?branch=add-lazy-url-matcher-test)](http://travis-ci.org/l3l0/Silex)

---------------------------------------------------------------------------

by igorw at 2012-06-30T12:45:18Z

Nice 👍

Also, how about adding this to .travis.yml:

    script: phpunit --coverage-text

---------------------------------------------------------------------------

by l3l0 at 2012-06-30T14:39:59Z

@igorw Ok I tried but error appear for php 5.3 cause try to cover all code under src even traits: http://travis-ci.org/#!/l3l0/Silex/jobs/1743756

I removed "--coverage-text" in next commit 1201230

Commits
-------

32ca5b51 Do not care about `mailer` service changes
efd3757d Avoid Swift Mailer initialization if possible

Discussion
----------

Avoid Swift Mailer initialization if possible

The finish() filter flushing spool messages after each request
caused Swift Mailer to be initialized and all services in this
provider to be instantiated.

Doing all this work takes time and is potentially unnecessary,
since only a small number of all requests queue messages for sending.

The time it takes to initialize swiftmailer and all services is between
1 and 2ms on the 2 machines I tested on.
This seems like a big price to pay for just including a provider
that does nothing for most requests.

Until now we tried to detect `mailer` service changes,
and always flushed messages for them, just to be safe.

To keep things simple, we don't do this anymore.
If `mailer` gets replaced by another service, flushing will
fail as expected. People should not replace it.