<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.1.3" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
	<title>Comments on: Serialization issues in Zend_Acl</title>
	<link>http://www.oeic.net/oeic/2007/06/07/serialization-issues-in-zend_acl/</link>
	<description>Just another WordPress weblog</description>
	<pubDate>Fri, 10 Sep 2010 04:05:58 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.1.3</generator>

	<item>
		<title>By: eKini Web Development Blog</title>
		<link>http://www.oeic.net/oeic/2007/06/07/serialization-issues-in-zend_acl/#comment-116</link>
		<author>eKini Web Development Blog</author>
		<pubDate>Wed, 03 Oct 2007 03:45:46 +0000</pubDate>
		<guid>http://www.oeic.net/oeic/2007/06/07/serialization-issues-in-zend_acl/#comment-116</guid>
					<description>Hello, 
thanks for this post... i am trying to learn Zend_Acl....
in your approach, you would serialize and then base64_encode() the ACL Object and then insert it into the DB.
is my assumption correct?
that the serialized ACL object in the DB will be side-by-side with the username/user ID? So that when the user logs in again, i would retrieve the ACL Object and use it again?
with that assumption, i have some questions. What if i wanted to update the ACL for all "members", how would I do that? when the ACL Object is already stored as string in the database? won't the ACL Object contain the old permissions?
I am confused on the way I should handle Zend_ACL...
Maybe you could post a step-by-step procedure of your approach? something like a flow-chart but in textual form :)

again, thanks for this post!</description>
		<content:encoded><![CDATA[<p>Hello,<br />
thanks for this post&#8230; i am trying to learn Zend_Acl&#8230;.<br />
in your approach, you would serialize and then base64_encode() the ACL Object and then insert it into the DB.<br />
is my assumption correct?<br />
that the serialized ACL object in the DB will be side-by-side with the username/user ID? So that when the user logs in again, i would retrieve the ACL Object and use it again?<br />
with that assumption, i have some questions. What if i wanted to update the ACL for all &#8220;members&#8221;, how would I do that? when the ACL Object is already stored as string in the database? won&#8217;t the ACL Object contain the old permissions?<br />
I am confused on the way I should handle Zend_ACL&#8230;<br />
Maybe you could post a step-by-step procedure of your approach? something like a flow-chart but in textual form <img src='http://www.oeic.net/oeic/blog/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
<p>again, thanks for this post!</p>
]]></content:encoded>
				</item>
	<item>
		<title>By: steve</title>
		<link>http://www.oeic.net/oeic/2007/06/07/serialization-issues-in-zend_acl/#comment-117</link>
		<author>steve</author>
		<pubDate>Wed, 03 Oct 2007 19:38:03 +0000</pubDate>
		<guid>http://www.oeic.net/oeic/2007/06/07/serialization-issues-in-zend_acl/#comment-117</guid>
					<description>Your assumption is indeed correct, but as mentioned at the end of the post, it might not be necessary to base64_encode() your serialized ACL object. Only testing in your environment will confirm if it is necessary or not, though the overhead of encoding/decoding might not be so much.

You're also correct that in my case, I have a serialized ACL object in the database along side each user ID. However, this approach isn't appropriate for each application. For instance, if you wanted to update the resources available for each member, you would have to update the ACL object stored in each row of your database by rebuilding the ACL object in PHP, then doing a SQL UPDATE. If you have a static, defined list of resources and roles, you may consider storing your ACL as a single row in a "Permissions" database table, or in a text file, or some other persistent state. My approach might not be the best for every application, but it fit my needs.

Perhaps I'll write up a tutorial on Zend_ACL that is more design focused, but I'd recommend taking a look at Simon Mundy's nuts and bolts tutorial here: http://devzone.zend.com/node/view/id/1665</description>
		<content:encoded><![CDATA[<p>Your assumption is indeed correct, but as mentioned at the end of the post, it might not be necessary to base64_encode() your serialized ACL object. Only testing in your environment will confirm if it is necessary or not, though the overhead of encoding/decoding might not be so much.</p>
<p>You&#8217;re also correct that in my case, I have a serialized ACL object in the database along side each user ID. However, this approach isn&#8217;t appropriate for each application. For instance, if you wanted to update the resources available for each member, you would have to update the ACL object stored in each row of your database by rebuilding the ACL object in PHP, then doing a SQL UPDATE. If you have a static, defined list of resources and roles, you may consider storing your ACL as a single row in a &#8220;Permissions&#8221; database table, or in a text file, or some other persistent state. My approach might not be the best for every application, but it fit my needs.</p>
<p>Perhaps I&#8217;ll write up a tutorial on Zend_ACL that is more design focused, but I&#8217;d recommend taking a look at Simon Mundy&#8217;s nuts and bolts tutorial here: <a href="http://devzone.zend.com/node/view/id/1665" rel="nofollow">http://devzone.zend.com/node/view/id/1665</a></p>
]]></content:encoded>
				</item>
	<item>
		<title>By: John Reader</title>
		<link>http://www.oeic.net/oeic/2007/06/07/serialization-issues-in-zend_acl/#comment-498</link>
		<author>John Reader</author>
		<pubDate>Fri, 25 Jan 2008 23:13:46 +0000</pubDate>
		<guid>http://www.oeic.net/oeic/2007/06/07/serialization-issues-in-zend_acl/#comment-498</guid>
					<description>I wish I had read this earlier in 2007.  This bug bit a website and took hours to nail down.  base64 to the rescue!</description>
		<content:encoded><![CDATA[<p>I wish I had read this earlier in 2007.  This bug bit a website and took hours to nail down.  base64 to the rescue!</p>
]]></content:encoded>
				</item>
	<item>
		<title>By: itlong</title>
		<link>http://www.oeic.net/oeic/2007/06/07/serialization-issues-in-zend_acl/#comment-779</link>
		<author>itlong</author>
		<pubDate>Tue, 04 Mar 2008 05:21:24 +0000</pubDate>
		<guid>http://www.oeic.net/oeic/2007/06/07/serialization-issues-in-zend_acl/#comment-779</guid>
					<description>where the code,and I can't read it.</description>
		<content:encoded><![CDATA[<p>where the code,and I can&#8217;t read it.</p>
]]></content:encoded>
				</item>
	<item>
		<title>By: 網站製作學習誌 &#187; [Web] 連結分享</title>
		<link>http://www.oeic.net/oeic/2007/06/07/serialization-issues-in-zend_acl/#comment-6837</link>
		<author>網站製作學習誌 &#187; [Web] 連結分享</author>
		<pubDate>Wed, 25 Nov 2009 02:44:11 +0000</pubDate>
		<guid>http://www.oeic.net/oeic/2007/06/07/serialization-issues-in-zend_acl/#comment-6837</guid>
					<description>[...] OEIC » Serialization issues in Zend_Acl [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] OEIC » Serialization issues in Zend_Acl [&#8230;]</p>
]]></content:encoded>
				</item>
</channel>
</rss>
