<?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: &#8220;Booking Modified By Another User&#8221; Error</title>
	<atom:link href="http://blog.coltcooper.com/2009/11/booking-modified-by-another-user-error/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.coltcooper.com/2009/11/booking-modified-by-another-user-error/</link>
	<description></description>
	<lastBuildDate>Mon, 01 Feb 2010 12:46:47 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
	<item>
		<title>By: Val Putyatina</title>
		<link>http://blog.coltcooper.com/2009/11/booking-modified-by-another-user-error/comment-page-1/#comment-46</link>
		<dc:creator>Val Putyatina</dc:creator>
		<pubDate>Mon, 01 Feb 2010 12:46:47 +0000</pubDate>
		<guid isPermaLink="false">http://blog.coltcooper.com/?p=19#comment-46</guid>
		<description>interesting.. but we have some errors with session. 
THe first one was Journey Overlap - but we certanly send two different  
journey keys. And what was interesting: we&#039;ve got this error only in TEST 
enviroment. It turned out, that setting of PROD and TEST enviroments 
were different only by one parameter: allowed time interval between flights. 
(on PROD it was about 2 hours and all was alright), but when we set same 
value on TEST - we&#039;ve got this error. But now it seems like it&#039;s OK.
And we&#039;ve got another error on TEST while commiting a booking: duplicate 
booking (if we test same citypairs some times running). Only cleaning of 
session help to avoid this error.</description>
		<content:encoded><![CDATA[<p>interesting.. but we have some errors with session.<br />
THe first one was Journey Overlap &#8211; but we certanly send two different<br />
journey keys. And what was interesting: we&#8217;ve got this error only in TEST<br />
enviroment. It turned out, that setting of PROD and TEST enviroments<br />
were different only by one parameter: allowed time interval between flights.<br />
(on PROD it was about 2 hours and all was alright), but when we set same<br />
value on TEST &#8211; we&#8217;ve got this error. But now it seems like it&#8217;s OK.<br />
And we&#8217;ve got another error on TEST while commiting a booking: duplicate<br />
booking (if we test same citypairs some times running). Only cleaning of<br />
session help to avoid this error.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
