<?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:georss="http://www.georss.org/georss" xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#" xmlns:media="http://search.yahoo.com/mrss/"
		>
<channel>
	<title>Comments for Open Sourcery</title>
	<atom:link href="http://jcalcote.wordpress.com/comments/feed/" rel="self" type="application/rss+xml" />
	<link>http://jcalcote.wordpress.com</link>
	<description>Technology, Open Source and Identity</description>
	<lastBuildDate>Tue, 15 Dec 2009 15:20:59 +0000</lastBuildDate>
	<generator>http://wordpress.com/</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>Comment on Java HTTPS Client Issues by Aditya</title>
		<link>http://jcalcote.wordpress.com/2009/06/18/java-https-client-issues/#comment-414</link>
		<dc:creator>Aditya</dc:creator>
		<pubDate>Tue, 15 Dec 2009 15:20:59 +0000</pubDate>
		<guid isPermaLink="false">http://jcalcote.wordpress.com/?p=151#comment-414</guid>
		<description>Hi John,

Very informative posts. I have a request. Could you please provide an example of how to call a secure Webservice method using your code above?</description>
		<content:encoded><![CDATA[<p>Hi John,</p>
<p>Very informative posts. I have a request. Could you please provide an example of how to call a secure Webservice method using your code above?</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Installing Windows XP on a SATA Drive by Byhl</title>
		<link>http://jcalcote.wordpress.com/2008/01/05/installing-windows-xp-on-a-sata-drive/#comment-413</link>
		<dc:creator>Byhl</dc:creator>
		<pubDate>Wed, 09 Dec 2009 02:41:26 +0000</pubDate>
		<guid isPermaLink="false">http://jcalcote.wordpress.com/2008/01/05/installing-windows-xp-on-a-sata-drive/#comment-413</guid>
		<description>Hello John!

   Thank you so much for your help and intense work on the sata issue. I followed your instructions and it worked on the first attempt.

Well done!</description>
		<content:encoded><![CDATA[<p>Hello John!</p>
<p>   Thank you so much for your help and intense work on the sata issue. I followed your instructions and it worked on the first attempt.</p>
<p>Well done!</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on PUT or POST: The REST of the Story by A simple (but long-winded) guide to REST web services &#124; kill the radio</title>
		<link>http://jcalcote.wordpress.com/2008/10/16/put-or-post-the-rest-of-the-story/#comment-409</link>
		<dc:creator>A simple (but long-winded) guide to REST web services &#124; kill the radio</dc:creator>
		<pubDate>Tue, 01 Dec 2009 10:17:37 +0000</pubDate>
		<guid isPermaLink="false">http://jcalcote.wordpress.com/?p=97#comment-409</guid>
		<description>[...] something, you use &#8220;POST.&#8221; A RESTful web service uses other HTTP verbs as well, namely PUT and DELETE, and can also implement OPTIONS to show which methods are appropriate for a [...]</description>
		<content:encoded><![CDATA[<p>[...] something, you use &#8220;POST.&#8221; A RESTful web service uses other HTTP verbs as well, namely PUT and DELETE, and can also implement OPTIONS to show which methods are appropriate for a [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on RESTful Transactions by Adib Saikali</title>
		<link>http://jcalcote.wordpress.com/2009/08/06/restful-transactions/#comment-404</link>
		<dc:creator>Adib Saikali</dc:creator>
		<pubDate>Thu, 19 Nov 2009 21:55:00 +0000</pubDate>
		<guid isPermaLink="false">http://jcalcote.wordpress.com/?p=179#comment-404</guid>
		<description>trying again with square brackets so the blog does not eat
up the XML tags, replace all [] with angle brackets
below.

You can also version the accounts like this.

GET /accounts/chequing/11/latest 
    REDIRECT: /account/chequing/11/12 
GET /account/chequing/11/12 

balance=500

/account/chequing/11/12 is a url of the form /account/chequing/11/[versionNo]

REQUEST: GET /account/savings/14/latest
REDIRECT /account/saving/14/77
GET /account/saving/14/77

balance=5000

POST /transactions/


    [from]/account/savings/14/77[/from]
    [to]/account/chequing/11/12[/to]
    [amount]400[/amount]
[/transfer]

201 CREATED
Location: /transactions/888

You can now do 

GET /transactions/888
[transaction]
   [transfer]
      [from]/account/savings/14/77[/from]
      [to]/account/chequing/11/12[/to]
      [amount]400[/amount]
   [/transfer]
   [result]
      [from id=&quot;/account/savings/14/78&quot;]4600[/from]
      [to id=&quot;/account/savings/11/13&quot;]9000[/from]
   [/result]
[/transaction]



Some Scenarios:

1) If there POST is posted more than once then the version
mismatch will be detected and the server can redirect
the client to another URI such as /transaction/versionMismatch which has an error message saying
the versions did not match

2) If the any of the accounts changed since I got the
acctual representation of the latest version version 
mistmatch occurs and the tx fails

I have not thought of all the edge cases and if this could work, but this is very similar to how hibernate 
does optimistic locking, I think it can probably be 
made to work.</description>
		<content:encoded><![CDATA[<p>trying again with square brackets so the blog does not eat<br />
up the XML tags, replace all [] with angle brackets<br />
below.</p>
<p>You can also version the accounts like this.</p>
<p>GET /accounts/chequing/11/latest<br />
    REDIRECT: /account/chequing/11/12<br />
GET /account/chequing/11/12 </p>
<p>balance=500</p>
<p>/account/chequing/11/12 is a url of the form /account/chequing/11/[versionNo]</p>
<p>REQUEST: GET /account/savings/14/latest<br />
REDIRECT /account/saving/14/77<br />
GET /account/saving/14/77</p>
<p>balance=5000</p>
<p>POST /transactions/</p>
<p>    [from]/account/savings/14/77[/from]<br />
    [to]/account/chequing/11/12[/to]<br />
    [amount]400[/amount]<br />
[/transfer]</p>
<p>201 CREATED<br />
Location: /transactions/888</p>
<p>You can now do </p>
<p>GET /transactions/888<br />
[transaction]<br />
   [transfer]<br />
      [from]/account/savings/14/77[/from]<br />
      [to]/account/chequing/11/12[/to]<br />
      [amount]400[/amount]<br />
   [/transfer]<br />
   [result]<br />
      [from id="/account/savings/14/78"]4600[/from]<br />
      [to id="/account/savings/11/13"]9000[/from]<br />
   [/result]<br />
[/transaction]</p>
<p>Some Scenarios:</p>
<p>1) If there POST is posted more than once then the version<br />
mismatch will be detected and the server can redirect<br />
the client to another URI such as /transaction/versionMismatch which has an error message saying<br />
the versions did not match</p>
<p>2) If the any of the accounts changed since I got the<br />
acctual representation of the latest version version<br />
mistmatch occurs and the tx fails</p>
<p>I have not thought of all the edge cases and if this could work, but this is very similar to how hibernate<br />
does optimistic locking, I think it can probably be<br />
made to work.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on RESTful Transactions by Adib Saikali</title>
		<link>http://jcalcote.wordpress.com/2009/08/06/restful-transactions/#comment-403</link>
		<dc:creator>Adib Saikali</dc:creator>
		<pubDate>Thu, 19 Nov 2009 21:28:23 +0000</pubDate>
		<guid isPermaLink="false">http://jcalcote.wordpress.com/?p=179#comment-403</guid>
		<description>Opps my XML tags around the request and response for a tx post got eaten up by the blog engine, ah I guess you need to view source to see them.</description>
		<content:encoded><![CDATA[<p>Opps my XML tags around the request and response for a tx post got eaten up by the blog engine, ah I guess you need to view source to see them.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on RESTful Transactions by Adib Saikali</title>
		<link>http://jcalcote.wordpress.com/2009/08/06/restful-transactions/#comment-402</link>
		<dc:creator>Adib Saikali</dc:creator>
		<pubDate>Thu, 19 Nov 2009 21:26:45 +0000</pubDate>
		<guid isPermaLink="false">http://jcalcote.wordpress.com/?p=179#comment-402</guid>
		<description>You can also version the accounts like this.

GET /accounts/chequing/11/latest 
    REDIRECT: /account/chequing/11/12 
GET /account/chequing/11/12 

balance=500

/account/chequing/11/12 is a url of the form /account/chequing/11/{versionNo}

REQUEST: GET /account/savings/14/latest
REDIRECT /account/saving/14/77
GET /account/saving/14/77

balance=5000

POST /transactions/


    /account/savings/14/77
    /account/chequing/11/12
    400


201 CREATED
Location: /transactions/888

GET /transactions/888

   
      /account/savings/14/77
      /account/chequing/11/12
      400
   
   
      4600
      900
   


You can now do GET/

Some Scenarios:

1) If there POST is posted more than once then the version
mismatch will be detected and the server can redirect
the client to another URI such as /transaction/versionMismatch which has an error message saying
the versions did not match

2) If the any of the accounts changed since I got the
acctual representation of the latest version version 
mistmatch occurs and the tx fails

I have not thought of all the edge cases and if this could work, but this is very similar to how hibernate 
does optimistic locking, I think it can probably be 
made to work.</description>
		<content:encoded><![CDATA[<p>You can also version the accounts like this.</p>
<p>GET /accounts/chequing/11/latest<br />
    REDIRECT: /account/chequing/11/12<br />
GET /account/chequing/11/12 </p>
<p>balance=500</p>
<p>/account/chequing/11/12 is a url of the form /account/chequing/11/{versionNo}</p>
<p>REQUEST: GET /account/savings/14/latest<br />
REDIRECT /account/saving/14/77<br />
GET /account/saving/14/77</p>
<p>balance=5000</p>
<p>POST /transactions/</p>
<p>    /account/savings/14/77<br />
    /account/chequing/11/12<br />
    400</p>
<p>201 CREATED<br />
Location: /transactions/888</p>
<p>GET /transactions/888</p>
<p>      /account/savings/14/77<br />
      /account/chequing/11/12<br />
      400</p>
<p>      4600<br />
      900</p>
<p>You can now do GET/</p>
<p>Some Scenarios:</p>
<p>1) If there POST is posted more than once then the version<br />
mismatch will be detected and the server can redirect<br />
the client to another URI such as /transaction/versionMismatch which has an error message saying<br />
the versions did not match</p>
<p>2) If the any of the accounts changed since I got the<br />
acctual representation of the latest version version<br />
mistmatch occurs and the tx fails</p>
<p>I have not thought of all the edge cases and if this could work, but this is very similar to how hibernate<br />
does optimistic locking, I think it can probably be<br />
made to work.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Getting the Most Out of Your HTPC by Thiwa</title>
		<link>http://jcalcote.wordpress.com/2008/09/29/getting-the-most-out-of-your-htpc/#comment-401</link>
		<dc:creator>Thiwa</dc:creator>
		<pubDate>Wed, 18 Nov 2009 20:36:30 +0000</pubDate>
		<guid isPermaLink="false">http://jcalcote.wordpress.com/?p=56#comment-401</guid>
		<description>Good Job &amp; Thank You Share This....</description>
		<content:encoded><![CDATA[<p>Good Job &amp; Thank You Share This&#8230;.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Java Https Key Setup by Arun</title>
		<link>http://jcalcote.wordpress.com/2009/06/19/java-https-key-setup/#comment-400</link>
		<dc:creator>Arun</dc:creator>
		<pubDate>Mon, 16 Nov 2009 21:39:45 +0000</pubDate>
		<guid isPermaLink="false">http://jcalcote.wordpress.com/?p=169#comment-400</guid>
		<description>Thanks for this great pointer here</description>
		<content:encoded><![CDATA[<p>Thanks for this great pointer here</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Getting the Most Out of Your HTPC by mike</title>
		<link>http://jcalcote.wordpress.com/2008/09/29/getting-the-most-out-of-your-htpc/#comment-399</link>
		<dc:creator>mike</dc:creator>
		<pubDate>Sat, 14 Nov 2009 02:21:38 +0000</pubDate>
		<guid isPermaLink="false">http://jcalcote.wordpress.com/?p=56#comment-399</guid>
		<description>Hi John, Thanks!</description>
		<content:encoded><![CDATA[<p>Hi John, Thanks!</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Getting the Most Out of Your HTPC by John Calcote</title>
		<link>http://jcalcote.wordpress.com/2008/09/29/getting-the-most-out-of-your-htpc/#comment-397</link>
		<dc:creator>John Calcote</dc:creator>
		<pubDate>Thu, 05 Nov 2009 21:56:59 +0000</pubDate>
		<guid isPermaLink="false">http://jcalcote.wordpress.com/?p=56#comment-397</guid>
		<description>@Mike: Did a little research. This card sounds perfect:

http://www.newegg.com/Product/Product.aspx?Item=N82E16815100041

A steal at 59 bucks, but it doesn&#039;t work with AVerMedia&#039;s media center software - only with WMC or other general purpose TV software packages.</description>
		<content:encoded><![CDATA[<p>@Mike: Did a little research. This card sounds perfect:</p>
<p><a href="http://www.newegg.com/Product/Product.aspx?Item=N82E16815100041" rel="nofollow">http://www.newegg.com/Product/Product.aspx?Item=N82E16815100041</a></p>
<p>A steal at 59 bucks, but it doesn&#8217;t work with AVerMedia&#8217;s media center software &#8211; only with WMC or other general purpose TV software packages.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
