<?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: Solving The HTTP Double-Post Dilema</title>
	<atom:link href="http://www.newthink.net/2007/03/06/solving-the-double-post-dilema/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.newthink.net/2007/03/06/solving-the-double-post-dilema/</link>
	<description>Less Talk. More Do.</description>
	<lastBuildDate>Wed, 13 Jul 2011 00:09:17 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.1</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Rene</title>
		<link>http://www.newthink.net/2007/03/06/solving-the-double-post-dilema/comment-page-1/#comment-13988</link>
		<dc:creator>Rene</dc:creator>
		<pubDate>Wed, 13 Jul 2011 00:09:17 +0000</pubDate>
		<guid isPermaLink="false">http://newthink.net/blog/2007/03/06/solving-the-double-post-dilema/#comment-13988</guid>
		<description>Depending on everyones application it&#039;s not allways possible to send headers when ever I want/need. If you already go into storing stuff in SESSION, I suggest another approach:
in your form set a hidden tag with a random number as a value (or you can use UNIX timestamp also). Now each time you get a form submit you check:
1) if the timestamp you got from POST isn&#039;t in the SESSION or it&#039;s different form the one in SESSION then it&#039;s the first or new POST and you store data into DB. NB! And you now store this timestamp in SESSION.
2) if the timestamp matches the one already in SESSION you know it&#039;s a repost and you discard it.</description>
		<content:encoded><![CDATA[<p>Depending on everyones application it&#8217;s not allways possible to send headers when ever I want/need. If you already go into storing stuff in SESSION, I suggest another approach:<br />
in your form set a hidden tag with a random number as a value (or you can use UNIX timestamp also). Now each time you get a form submit you check:<br />
1) if the timestamp you got from POST isn&#8217;t in the SESSION or it&#8217;s different form the one in SESSION then it&#8217;s the first or new POST and you store data into DB. NB! And you now store this timestamp in SESSION.<br />
2) if the timestamp matches the one already in SESSION you know it&#8217;s a repost and you discard it.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: shafi</title>
		<link>http://www.newthink.net/2007/03/06/solving-the-double-post-dilema/comment-page-1/#comment-6677</link>
		<dc:creator>shafi</dc:creator>
		<pubDate>Thu, 10 Jun 2010 18:07:31 +0000</pubDate>
		<guid isPermaLink="false">http://newthink.net/blog/2007/03/06/solving-the-double-post-dilema/#comment-6677</guid>
		<description>wow... i never thought i could do like this way.. great thinking man. if this is from ur brain. i admire u. thanks a lot</description>
		<content:encoded><![CDATA[<p>wow&#8230; i never thought i could do like this way.. great thinking man. if this is from ur brain. i admire u. thanks a lot</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Android</title>
		<link>http://www.newthink.net/2007/03/06/solving-the-double-post-dilema/comment-page-1/#comment-1002</link>
		<dc:creator>Android</dc:creator>
		<pubDate>Thu, 13 Nov 2008 15:16:28 +0000</pubDate>
		<guid isPermaLink="false">http://newthink.net/blog/2007/03/06/solving-the-double-post-dilema/#comment-1002</guid>
		<description>Thanks a lot. You solved my problem.</description>
		<content:encoded><![CDATA[<p>Thanks a lot. You solved my problem.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

