<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:series="http://unfoldingneurons.com/"
		>
<channel>
	<title>Comments on: PHP Serialize, What&#8217;s it Do? What&#8217;s it For?</title>
	<atom:link href="http://blog.ninedays.org/2008/05/11/php-serialize-unserialize-whats-it-do-whats-it-for/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.ninedays.org/2008/05/11/php-serialize-unserialize-whats-it-do-whats-it-for/</link>
	<description>web development, photography, tutorials and adventure</description>
	<lastBuildDate>Wed, 25 Aug 2010 05:58:24 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
	<item>
		<title>By: Jules Manson</title>
		<link>http://blog.ninedays.org/2008/05/11/php-serialize-unserialize-whats-it-do-whats-it-for/comment-page-1/#comment-2778</link>
		<dc:creator>Jules Manson</dc:creator>
		<pubDate>Wed, 25 Aug 2010 05:58:24 +0000</pubDate>
		<guid isPermaLink="false">http://blog.ninedays.org/?p=265#comment-2778</guid>
		<description>&lt;p&gt;Thank y0u anyway and i figured it out myself. I loved your article and I now know what serialize is for. By the way the reason I am now responding is because once in a while I will google my name and survey past comments I have made at other sites. Its kind of neat to see one&#039;s own web history.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>Thank y0u anyway and i figured it out myself. I loved your article and I now know what serialize is for. By the way the reason I am now responding is because once in a while I will google my name and survey past comments I have made at other sites. Its kind of neat to see one&#8217;s own web history.</p>]]></content:encoded>
	</item>
	<item>
		<title>By: Terri Ann</title>
		<link>http://blog.ninedays.org/2008/05/11/php-serialize-unserialize-whats-it-do-whats-it-for/comment-page-1/#comment-2723</link>
		<dc:creator>Terri Ann</dc:creator>
		<pubDate>Thu, 03 Jun 2010 20:23:32 +0000</pubDate>
		<guid isPermaLink="false">http://blog.ninedays.org/?p=265#comment-2723</guid>
		<description>&lt;p&gt;To be honest Jules you kind of lost me there. But even if you didn&#039;t lose me on it I don&#039;t think I have the answer to that question.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>To be honest Jules you kind of lost me there. But even if you didn&#8217;t lose me on it I don&#8217;t think I have the answer to that question.</p>]]></content:encoded>
	</item>
	<item>
		<title>By: Jules Manson</title>
		<link>http://blog.ninedays.org/2008/05/11/php-serialize-unserialize-whats-it-do-whats-it-for/comment-page-1/#comment-2715</link>
		<dc:creator>Jules Manson</dc:creator>
		<pubDate>Sun, 23 May 2010 17:51:48 +0000</pubDate>
		<guid isPermaLink="false">http://blog.ninedays.org/?p=265#comment-2715</guid>
		<description>&lt;p&gt;Please bare with me. This will only take one minute.&lt;/p&gt;

&lt;p&gt;I created my own PHP template parser whereby my site uses one HTML template sprinkled with {TAGNAME} where tagname is actually different tag names that the parser will replace with functions or strings that I supply elsewhere or substitute data from MySQL database.  This keeps my PHP completely separated from the HTML. All parser tags are also associated array elements. For example on my HTML template I have a tag {CRUMBS}. In a controller class I define this $tags[&#039;CRUMBS&#039;] = &quot;[php] return Breadcrumbs::inst();&quot;; the inst() function simply instantiates my Breadcrumbs class. The &quot;[php]&quot; tells my template parser class to use the eval() function in order to treat the string as a PHP function. The end product of the function is to create a string that browsers recognize as several links of places visited on  my site. My question is this: Could I have simply serialized the function instead of using eval()?&lt;/p&gt;

&lt;p&gt;I hope I didn&#039;t lose you.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>Please bare with me. This will only take one minute.</p>

<p>I created my own PHP template parser whereby my site uses one HTML template sprinkled with {TAGNAME} where tagname is actually different tag names that the parser will replace with functions or strings that I supply elsewhere or substitute data from MySQL database.  This keeps my PHP completely separated from the HTML. All parser tags are also associated array elements. For example on my HTML template I have a tag {CRUMBS}. In a controller class I define this $tags['CRUMBS'] = &#8220;[php] return Breadcrumbs::inst();&#8221;; the inst() function simply instantiates my Breadcrumbs class. The &#8220;[php]&#8221; tells my template parser class to use the eval() function in order to treat the string as a PHP function. The end product of the function is to create a string that browsers recognize as several links of places visited on  my site. My question is this: Could I have simply serialized the function instead of using eval()?</p>

<p>I hope I didn&#8217;t lose you.</p>]]></content:encoded>
	</item>
	<item>
		<title>By: danilo di moia</title>
		<link>http://blog.ninedays.org/2008/05/11/php-serialize-unserialize-whats-it-do-whats-it-for/comment-page-1/#comment-2690</link>
		<dc:creator>danilo di moia</dc:creator>
		<pubDate>Thu, 08 Apr 2010 09:08:59 +0000</pubDate>
		<guid isPermaLink="false">http://blog.ninedays.org/?p=265#comment-2690</guid>
		<description>&lt;p&gt;thanks for very clear explanation :)&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>thanks for very clear explanation :)</p>]]></content:encoded>
	</item>
	<item>
		<title>By: Enigma415</title>
		<link>http://blog.ninedays.org/2008/05/11/php-serialize-unserialize-whats-it-do-whats-it-for/comment-page-1/#comment-2651</link>
		<dc:creator>Enigma415</dc:creator>
		<pubDate>Wed, 10 Mar 2010 07:18:00 +0000</pubDate>
		<guid isPermaLink="false">http://blog.ninedays.org/?p=265#comment-2651</guid>
		<description>&lt;p&gt;I may add: if you wish to use these functions with client data ($&lt;em&gt;GET &amp; $&lt;/em&gt;POST, etc), preg_replace(&#039;/[^a-zA-Z0-9]&#039;, &#039;&#039;, $clientdata). That -should- make the sent string(s) safe for programmical use. Use that before you serialize() the data.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>I may add: if you wish to use these functions with client data ($<em>GET &amp; $</em>POST, etc), preg_replace(&#8216;/[^a-zA-Z0-9]&#8216;, &#8221;, $clientdata). That -should- make the sent string(s) safe for programmical use. Use that before you serialize() the data.</p>]]></content:encoded>
	</item>
	<item>
		<title>By: dreftymac</title>
		<link>http://blog.ninedays.org/2008/05/11/php-serialize-unserialize-whats-it-do-whats-it-for/comment-page-1/#comment-2646</link>
		<dc:creator>dreftymac</dc:creator>
		<pubDate>Tue, 23 Feb 2010 01:31:24 +0000</pubDate>
		<guid isPermaLink="false">http://blog.ninedays.org/?p=265#comment-2646</guid>
		<description>&lt;p&gt;another alternative is to use base64 encoding to encode/decode the serialized data if you are worried about messing up your database values or transmitting the serialized data over the wire. disgusts&lt;em&gt;uncover&lt;/em&gt;akin_umbriel&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>another alternative is to use base64 encoding to encode/decode the serialized data if you are worried about messing up your database values or transmitting the serialized data over the wire. disgusts<em>uncover</em>akin_umbriel</p>]]></content:encoded>
	</item>
	<item>
		<title>By: Marc</title>
		<link>http://blog.ninedays.org/2008/05/11/php-serialize-unserialize-whats-it-do-whats-it-for/comment-page-1/#comment-2645</link>
		<dc:creator>Marc</dc:creator>
		<pubDate>Sun, 21 Feb 2010 20:45:42 +0000</pubDate>
		<guid isPermaLink="false">http://blog.ninedays.org/?p=265#comment-2645</guid>
		<description>&lt;p&gt;well explained !&lt;/p&gt;

&lt;p&gt;here is a tool I often use in my job... to decode quickly serialized data... Indeed, serialised datas are good for system, but uneasy for us to read..&lt;/p&gt;

&lt;p&gt;http://unserialize.net&lt;/p&gt;

&lt;p&gt;Thanks again !&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>well explained !</p>

<p>here is a tool I often use in my job&#8230; to decode quickly serialized data&#8230; Indeed, serialised datas are good for system, but uneasy for us to read..</p>

<p><a href="http://unserialize.net" rel="nofollow">http://unserialize.net</a></p>

<p>Thanks again !</p>]]></content:encoded>
	</item>
	<item>
		<title>By: Mark Shercliff</title>
		<link>http://blog.ninedays.org/2008/05/11/php-serialize-unserialize-whats-it-do-whats-it-for/comment-page-1/#comment-2632</link>
		<dc:creator>Mark Shercliff</dc:creator>
		<pubDate>Wed, 03 Feb 2010 11:23:04 +0000</pubDate>
		<guid isPermaLink="false">http://blog.ninedays.org/?p=265#comment-2632</guid>
		<description>&lt;p&gt;Best explanation I&#039;ve read - thank you!&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>Best explanation I&#8217;ve read &#8211; thank you!</p>]]></content:encoded>
	</item>
	<item>
		<title>By: sickbro</title>
		<link>http://blog.ninedays.org/2008/05/11/php-serialize-unserialize-whats-it-do-whats-it-for/comment-page-1/#comment-2526</link>
		<dc:creator>sickbro</dc:creator>
		<pubDate>Thu, 05 Nov 2009 13:44:50 +0000</pubDate>
		<guid isPermaLink="false">http://blog.ninedays.org/?p=265#comment-2526</guid>
		<description>&lt;p&gt;Mate, this was just the information I was after. Thanks very much for your time writing this.&lt;/p&gt;

&lt;p&gt;As a side note, unserialize() should NEVER be used on user input, as the security implications can be very serious. See SyScan / Blackhat USA 2009 and &quot;Month of PHP Bugs&quot;&lt;/p&gt;

&lt;p&gt;Wow... I&#039;m writing back to a 1 year old blog post lol&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>Mate, this was just the information I was after. Thanks very much for your time writing this.</p>

<p>As a side note, unserialize() should NEVER be used on user input, as the security implications can be very serious. See SyScan / Blackhat USA 2009 and &#8220;Month of PHP Bugs&#8221;</p>

<p>Wow&#8230; I&#8217;m writing back to a 1 year old blog post lol</p>]]></content:encoded>
	</item>
	<item>
		<title>By: Anders</title>
		<link>http://blog.ninedays.org/2008/05/11/php-serialize-unserialize-whats-it-do-whats-it-for/comment-page-1/#comment-2420</link>
		<dc:creator>Anders</dc:creator>
		<pubDate>Tue, 07 Jul 2009 20:45:13 +0000</pubDate>
		<guid isPermaLink="false">http://blog.ninedays.org/?p=265#comment-2420</guid>
		<description>&lt;p&gt;Thanks for explaining this.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>Thanks for explaining this.</p>]]></content:encoded>
	</item>
</channel>
</rss>
