[docs] Clarify wording of controllers-in-classes to create object
merged branch igorw/oop-wording (PR #582)

This PR was merged into the master branch.

Commits
-------

d784eae [docs] Clarify wording of controllers-in-classes to create object

Discussion
----------

[docs] Clarify wording of controllers-in-classes to create object
Update doc/providers/security.rst

Fixed spelling mistake
merged branch robincawser/patch-1 (PR #583)

This PR was merged into the master branch.

Commits
-------

661d632 Update doc/providers/security.rst

Discussion
----------

Update doc/providers/security.rst

Fixed spelling mistake

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

by igorw at 2013-01-15T13:26:30Z

:+1:
Update doc/usage.rst

I'm new to http methods other than GET and POST and spent a good few minutes searching google for PUT DELETE... So I thought I'd separate them somehow in the docs
Fix route name in security service doc
merged branch faost/fixdoc (PR #588)

This PR was merged into the master branch.

Commits
-------

853a16a Fix route name in security service doc

Discussion
----------

Fix route name in security service doc

Fix a little bit confusing mistake in security doc.
Update doc/providers/security.rst

Take 2 on sorting out the parenthesis in the registration code snippet.
merged branch KodoArkivo/master (PR #591)

This PR was merged into the master branch.

Commits
-------

ae7daed Update doc/providers/security.rst

Discussion
----------

Take 2 on sorting out the parenthesis in the registration code snippet.

Take 2 on sorting out the parenthesis in the registration code snippet.
merged branch robincawser/patch-2 (PR #586)

This PR was merged into the master branch.

Commits
-------

eded6c7 Update doc/usage.rst

Discussion
----------

Update doc/usage.rst

I'm new to http methods other than GET and POST and spent a good few minutes searching google for "PUT DELETE"... So I thought I'd separate them somehow in the docs.

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

by davedevelopment at 2013-01-16T13:41:49Z

:+1: might be better with a comma though?

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

by robincawser at 2013-01-16T13:53:08Z

Isn't the last item of a list usually separated with "or" or "and"?

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

by davedevelopment at 2013-01-16T14:01:25Z

Usually yes, not a big deal, but you never know, it might avoid people doing a google search for the "PUT or DELETE" HTTP method ;)
Minor WS fixes in documentation

Spaces at the end of line.
Update doc/providers/security.rst

Added closing bracket
Support 'security' and 'stateless' flags in security config
merged branch hakre/patch-2 (PR #593)

This PR was merged into the master branch.

Commits
-------

5e0a609 Minor WS fixes in documentation

Discussion
----------

Minor WS fixes in documentation

Spaces at the end of line.
merged branch robincawser/patch-3 (PR #595)

This PR was merged into the master branch.

Commits
-------

ff75c9e Update doc/providers/security.rst

Discussion
----------

Update doc/providers/security.rst

Added closing bracket
merged branch gigablah/security-flags (PR #573)

This PR was merged into the master branch.

Commits
-------

e21b380 Support 'security' and 'stateless' flags in security config

Discussion
----------

Support 'security' and 'stateless' flags in security config

`'security' => false` will disable the firewall (for a particular area) even if there are listeners configured.

`'stateless' => true` will prevent `ContextListener` from getting registered.

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

by davedevelopment at 2013-01-05T15:01:38Z

I'm not sure I understand what you'd use these flags for, perhaps some
documentation would be useful?
 On Jan 5, 2013 10:05 AM, "Chris Heng" <notifications@github.com> wrote:

> 'security' => false will disable the firewall even if there are listeners
> configured.
>
> 'stateless' => true will prevent ContextListener from getting registered.
> ------------------------------
> You can merge this Pull Request by running:
>
>   git pull https://github.com/gigablah/Silex security-flags
>
> Or view, comment on, or merge it at:
>
>   https://github.com/fabpot/Silex/pull/573
> Commit Summary
>
>    - Support 'security' and 'stateless' flags in security config
>
> File Changes
>
>    - *M* src/Silex/Provider/SecurityServiceProvider.php (10)
>
> Patch Links
>
>    - https://github.com/fabpot/Silex/pull/573.patch
>    - https://github.com/fabpot/Silex/pull/573.diff
>
>  —
> Reply to this email directly or view it on GitHub<https://github.com/fabpot/Silex/pull/573>.
>
>

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

by gigablah at 2013-01-05T15:30:13Z

These are the same flags you can use in Symfony2. I guess `'security' => false` by itself isn't too useful, but you could hypothetically do something like:

```php
$app->register(new SecurityServiceProvider(), array(
    'security.firewalls' => array(
        'api' => array(
            'pattern' => '^/api',
            'stateless' => true,
            'security' => !$app['debug'],
            'oauth' => true
        )
    )
));
```

Which will (a) turn off oauth access token authentication when you're debugging (b) turn off read/write on the session during authentication, which isn't wanted since the oauth access token is sent for each request.

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

by davedevelopment at 2013-01-06T20:48:20Z

Sorry, I think I got confused by the security flag, I understand the stateless one.

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

by stof at 2013-01-06T21:13:04Z

The goal of the ``security`` flag is to create a firewall pattern without firewall. The only reason for this is to whitelist a pattern by placing it before another pattern without having to create a crazy regex

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

by fabpot at 2013-01-18T15:00:19Z

Can you also update the documentation about these two new settings? Thanks.

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

by gigablah at 2013-01-19T04:37:08Z

It's done. Added a section for Stateless Authentication, and a tip for the `security` flag.
Sample user insert snippet.

The execute_query command to insert users into a sample database doesn't work with postgres due to the use of database specific string escape quotes. Changed to use the doctrine insert command which is less DB specific and better illustrates the use of DBAL.
merged branch KodoArkivo/patch-2 (PR #596)

This PR was merged into the master branch.

Commits
-------

d740c4e Sample user insert snippet.

Discussion
----------

Sample user insert snippet.

The execute_query command to insert users into a sample database doesn't work with postgres due to the use of database specific string escape quotes. Changed to use the doctrine insert command which is less DB specific and better illustrates the use of DBAL.

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

by stof at 2013-01-19T11:57:24Z

:+1:
Update doc/providers/serializer.rst

fixed links
merged branch jdreesen/patch-2 (PR #599)

This PR was merged into the master branch.

Commits
-------

61bbc74 Update doc/providers/serializer.rst

Discussion
----------

Update doc/providers/serializer.rst

fixed links

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

by igorw at 2013-01-20T00:48:17Z

:+1: thanks