<?xml version="1.0"?>
<rss version="2.0">
  <channel>
    <title>PHPDeveloper.org</title>
    <link>http://www.phpdeveloper.org</link>
    <description>Up-to-the Minute PHP News, views and community</description>
    <language>en-us</language>
    <pubDate>Wed, 22 May 2013 22:43:04 -0500</pubDate>
    <ttl>30</ttl>
    <item>
      <title><![CDATA[Johannes Schmitt's Blog: A New Killer Feature for Symfony2 Security]]></title>
      <guid>http://www.phpdeveloper.org/news/17065</guid>
      <link>http://www.phpdeveloper.org/news/17065</link>
      <description><![CDATA[<p>
<i>Johannes Schmitt</i> has <a href="http://blog.jmsyst.com/2011/10/new-killer-feature-for-symfony2.html">a new post</a> about his "killer feature" he's added to the security for <a href="http://symfony.com">Symfony2</a> framework (as a bundle) - a new customized expression-based query language that's compiled down to native PHP to make permissions checking simpler and faster.
</p>
<blockquote>
If you have used the Symfony2 Security Component to any modest degree, you will know that we have a quite heavy voting system which uses attributes like "IS_AUTHENTICATED_FULLY" to make authorization decisions. [...] If you are concerned about performance, then you should not be all too generous with the isGranted() calls. The second option would work as well, but writing a new voter each time you need to make a new check does not really seem ideal either. Fortunately, we can do better.
</blockquote>
<p>
He includes an example of this expression language in a direct isGranted() call, a string that checks to see if a user has three different roles, and a snippet showing the same thing in the docblock comment of a controller method. The second is a bit more complex, checking for an admin role or if the user is the one that should be deleted. You can <a href="https://github.com/schmittjoh/JMSSecurityExtraBundle/blob/master/Resources/doc/index.rst">find more doucmentation here</a>.
</p>]]></description>
      <pubDate>Mon, 31 Oct 2011 14:26:08 -0500</pubDate>
    </item>
    <item>
      <title><![CDATA[Edin Kadribasic's Blog: Serendipity on Lighty]]></title>
      <guid>http://www.phpdeveloper.org/news/7671</guid>
      <link>http://www.phpdeveloper.org/news/7671</link>
      <description><![CDATA[<p>
In a <a href="http://edin.dk/archives/34-Serendipity-on-Lighty.html">new post</a> <i>Edin Kadribasic</i> shares his method for getting a <a href="http://www.s9y.org/">Serendipity</a> (a popular PHP-based blogging system) website up and running on a <a href="http://www.lighttpd.net/">lighttpd server</a>.
</p>
<blockquote>
Well the basic install went pretty smoothly, but I wanted, of course, to use "friendly" URLs. For that Serendipity supplies .htaccess file with Apache mod_rewrite rules. With a little bit of effort it was possible for me to convert those into rewrite rules that lighttpd would understand.
</blockquote>
<p>
He <a href="http://edin.dk/archives/34-Serendipity-on-Lighty.html">includes</a> all of the rewrite rules lighttpd needs to mimic the responses of an Apache server in a rewrite-once statement, and a limitation on the files the server can send with an access-deny config line.
</p>]]></description>
      <pubDate>Sat, 21 Apr 2007 09:42:42 -0500</pubDate>
    </item>
  </channel>
</rss>
