﻿<?xml version="1.0" encoding="utf-8"?><rss version="2.0"><channel><title>Ayende @ Rahien</title><link>http://ayende.com</link><description>Ayende @ Rahien</description><copyright>Copyright (C) Ayende Rahien  2004 - 2021 (c) 2026</copyright><ttl>60</ttl><item><title>Ayende Rahien commented on Reading Erlang: CouchDB - From REST to Disk in a few function calls</title><description>Oh, that make sense, I got it the other way around
</description><link>http://ayende.com/3627/reading-erlang-couchdb-from-rest-to-disk-in-a-few-function-calls#comment2</link><guid>http://ayende.com/3627/reading-erlang-couchdb-from-rest-to-disk-in-a-few-function-calls#comment2</guid><pubDate>Sat, 04 Oct 2008 07:10:28 GMT</pubDate></item><item><title>Jan commented on Reading Erlang: CouchDB - From REST to Disk in a few function calls</title><description>Excellent, again, keep it up! :)
  
  
&gt; Not sure why this is important for PUT request, however. This make sense for POST (update) request, however.
  
  
In REST-lingo, POST creates new resources in a collection (where the server creates the name of the resource) and PUT updates existing resources or creates new "named"-resources (resources, where the client specifies the name of the resource).
  
  
Cheers,
  
Jan
  
--
</description><link>http://ayende.com/3627/reading-erlang-couchdb-from-rest-to-disk-in-a-few-function-calls#comment1</link><guid>http://ayende.com/3627/reading-erlang-couchdb-from-rest-to-disk-in-a-few-function-calls#comment1</guid><pubDate>Sat, 04 Oct 2008 07:05:23 GMT</pubDate></item></channel></rss>