<?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/"
		>
<channel>
	<title>Comments on: PHP: Sessions vs Cookies</title>
	<atom:link href="http://www.klovera.com/php-sessions-vs-cookies/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.klovera.com/php-sessions-vs-cookies/</link>
	<description>Just another WordPress weblog</description>
	<lastBuildDate>Tue, 07 Sep 2010 21:09:38 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	
	<item>
		<title>By: Rbrilliant</title>
		<link>http://www.klovera.com/php-sessions-vs-cookies/comment-page-1/#comment-1167</link>
		<dc:creator>Rbrilliant</dc:creator>
		<pubDate>Wed, 04 Aug 2010 15:28:57 +0000</pubDate>
		<guid isPermaLink="false">http://www.dustinsdesign.com/php-sessions-vs-cookies/#comment-1167</guid>
		<description>Nice concise article!</description>
		<content:encoded><![CDATA[<p>Nice concise article!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: arun</title>
		<link>http://www.klovera.com/php-sessions-vs-cookies/comment-page-1/#comment-569</link>
		<dc:creator>arun</dc:creator>
		<pubDate>Tue, 06 Apr 2010 12:00:40 +0000</pubDate>
		<guid isPermaLink="false">http://www.dustinsdesign.com/php-sessions-vs-cookies/#comment-569</guid>
		<description>very helpful .... 

but I have a question for you though ... can we use sessions and still support the &quot;keep me logged in&quot; feature? or do we have to use cookies for that?

thanks.</description>
		<content:encoded><![CDATA[<p>very helpful &#8230;. </p>
<p>but I have a question for you though &#8230; can we use sessions and still support the &#8220;keep me logged in&#8221; feature? or do we have to use cookies for that?</p>
<p>thanks.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Abe</title>
		<link>http://www.klovera.com/php-sessions-vs-cookies/comment-page-1/#comment-14</link>
		<dc:creator>Abe</dc:creator>
		<pubDate>Fri, 15 Jan 2010 02:09:44 +0000</pubDate>
		<guid isPermaLink="false">http://www.dustinsdesign.com/php-sessions-vs-cookies/#comment-14</guid>
		<description>@alapati

Sessions and cookie are stored in a very similar way.
The main difference is the simple fact users can&#039;t edit their own sessions as they are server based.

As a rule, this makes them more secure when dealing with sensetive information.

A great comparative article, thanks!</description>
		<content:encoded><![CDATA[<p>@alapati</p>
<p>Sessions and cookie are stored in a very similar way.<br />
The main difference is the simple fact users can&#8217;t edit their own sessions as they are server based.</p>
<p>As a rule, this makes them more secure when dealing with sensetive information.</p>
<p>A great comparative article, thanks!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: padmaja</title>
		<link>http://www.klovera.com/php-sessions-vs-cookies/comment-page-1/#comment-13</link>
		<dc:creator>padmaja</dc:creator>
		<pubDate>Thu, 05 Nov 2009 10:33:19 +0000</pubDate>
		<guid isPermaLink="false">http://www.dustinsdesign.com/php-sessions-vs-cookies/#comment-13</guid>
		<description>cookies means  to pass the information one page to another page in one application.
session means what changes made in an application browser</description>
		<content:encoded><![CDATA[<p>cookies means  to pass the information one page to another page in one application.<br />
session means what changes made in an application browser</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: alapati</title>
		<link>http://www.klovera.com/php-sessions-vs-cookies/comment-page-1/#comment-12</link>
		<dc:creator>alapati</dc:creator>
		<pubDate>Thu, 05 Nov 2009 10:24:58 +0000</pubDate>
		<guid isPermaLink="false">http://www.dustinsdesign.com/php-sessions-vs-cookies/#comment-12</guid>
		<description>from this i understand that cookies and sessions their are slight difference .sometimes sessions r stored like a cookie</description>
		<content:encoded><![CDATA[<p>from this i understand that cookies and sessions their are slight difference .sometimes sessions r stored like a cookie</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Rakshith</title>
		<link>http://www.klovera.com/php-sessions-vs-cookies/comment-page-1/#comment-11</link>
		<dc:creator>Rakshith</dc:creator>
		<pubDate>Tue, 03 Mar 2009 12:54:37 +0000</pubDate>
		<guid isPermaLink="false">http://www.dustinsdesign.com/php-sessions-vs-cookies/#comment-11</guid>
		<description>Nicely explained</description>
		<content:encoded><![CDATA[<p>Nicely explained</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Gabe</title>
		<link>http://www.klovera.com/php-sessions-vs-cookies/comment-page-1/#comment-10</link>
		<dc:creator>Gabe</dc:creator>
		<pubDate>Mon, 30 Jun 2008 08:43:16 +0000</pubDate>
		<guid isPermaLink="false">http://www.dustinsdesign.com/php-sessions-vs-cookies/#comment-10</guid>
		<description>Nice write up on that :)</description>
		<content:encoded><![CDATA[<p>Nice write up on that :)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dustin</title>
		<link>http://www.klovera.com/php-sessions-vs-cookies/comment-page-1/#comment-9</link>
		<dc:creator>Dustin</dc:creator>
		<pubDate>Fri, 25 Jan 2008 20:27:48 +0000</pubDate>
		<guid isPermaLink="false">http://www.dustinsdesign.com/php-sessions-vs-cookies/#comment-9</guid>
		<description>Nile, you are absolutely correct, using GET is easily hacked. There are other more complex options you could use. For example, you could store certain information about each client in a temporary location on the server (like their IP and login) and then check against that for each subsequent page. However, this would also be prone to security and performance issues. As with all security, on and off the web, the best method is to have multiple lines of defense.

In any event, with the standard being that cookies typically &lt;em&gt;are&lt;/em&gt;  enabled you can simply deny access to visitors who don&#039;t accept cookies with a polite message like &quot;To view this site you must first enable cookies in your browser&quot;. Then give some instruction on enabling them. That being said, always code to accommodate your target market and the technology they are actually using.</description>
		<content:encoded><![CDATA[<p>Nile, you are absolutely correct, using GET is easily hacked. There are other more complex options you could use. For example, you could store certain information about each client in a temporary location on the server (like their IP and login) and then check against that for each subsequent page. However, this would also be prone to security and performance issues. As with all security, on and off the web, the best method is to have multiple lines of defense.</p>
<p>In any event, with the standard being that cookies typically <em>are</em>  enabled you can simply deny access to visitors who don&#8217;t accept cookies with a polite message like &#8220;To view this site you must first enable cookies in your browser&#8221;. Then give some instruction on enabling them. That being said, always code to accommodate your target market and the technology they are actually using.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Nile</title>
		<link>http://www.klovera.com/php-sessions-vs-cookies/comment-page-1/#comment-8</link>
		<dc:creator>Nile</dc:creator>
		<pubDate>Fri, 25 Jan 2008 19:56:08 +0000</pubDate>
		<guid isPermaLink="false">http://www.dustinsdesign.com/php-sessions-vs-cookies/#comment-8</guid>
		<description>Well is there a more secure method then using get?
get is a pretty un-secure function and easy to hack.</description>
		<content:encoded><![CDATA[<p>Well is there a more secure method then using get?<br />
get is a pretty un-secure function and easy to hack.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
