<?xml version="1.0" encoding="utf-8"?><?xml-stylesheet title="XSL formatting" type="text/xsl" href="http://www.gandibar.net/feed/rss2/xslt" ?><rss version="2.0"
  xmlns:dc="http://purl.org/dc/elements/1.1/"
  xmlns:content="http://purl.org/rss/1.0/modules/content/"
  xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
  <title>Gandi Bar - Go API with Gandi!  - Comments</title>
  <link>http://www.gandibar.net/</link>
  <atom:link href="http://www.gandibar.net/feed/rss2/comments/388" rel="self" type="application/rss+xml"/>
  <description>Gandi blog, to share our opinions</description>
  <language>en</language>
  <pubDate>Thu, 28 Aug 2008 12:57:34 +0200</pubDate>
  <copyright></copyright>
  <docs>http://blogs.law.harvard.edu/tech/rss</docs>
  <generator>Dotclear</generator>
  
    
    
    <item>
    <title>Go API with Gandi! - Nicolas (Gandi)</title>
    <link>http://www.gandibar.net/post/2007/01/18/Go-API-with-Gandi#c70203</link>
    <guid isPermaLink="false">urn:md5:3ee72f8bcb833a29d94ff5509a146e7a</guid>
    <pubDate>Fri, 23 Feb 2007 16:12:31 +0100</pubDate>
    <dc:creator>Nicolas (Gandi)</dc:creator>
    
    <description>&lt;p&gt;Btw, we have just added a newsgroup to talk about it on nntp://groups.gandi.net or via &lt;a href=&quot;http://groups.gandi.net/group/gandi.en.api&quot; title=&quot;http://groups.gandi.net/group/gandi.en.api&quot; rel=&quot;nofollow&quot;&gt;http://groups.gandi.net/group/gandi...&lt;/a&gt;&lt;/p&gt;</description>
  </item>
      
    
    <item>
    <title>Go API with Gandi! - vincent</title>
    <link>http://www.gandibar.net/post/2007/01/18/Go-API-with-Gandi#c70200</link>
    <guid isPermaLink="false">urn:md5:12d199badf20a796ba6bac4f7a836b48</guid>
    <pubDate>Fri, 23 Feb 2007 16:05:15 +0100</pubDate>
    <dc:creator>vincent</dc:creator>
    
    <description>&lt;p&gt;We considered EPP as an alternative, along with soap, rest, xmlrpc, etc, the problem is that even if there is effectively a few open (and buggy) client libraries, there's absolutely no server implementation available (that may explain why every registry EPP implementation have different behaviors and specificities), so beside implementing our own EPP server, we should have implemented and supported n clients libs for n languages. EPP is a surely an accepted standard for communication between registries and registrars, but i don't know any registrar providing EPP to their clients (well, ok, some use RRP), and it's not really what we should call a 'light' protocol, xmlrpc, on the over hand, is really simple to implement and use (see &lt;a href=&quot;http://www.xmlrpc.com/&quot; title=&quot;http://www.xmlrpc.com/&quot; rel=&quot;nofollow&quot;&gt;http://www.xmlrpc.com/&lt;/a&gt;), and there's client and server implementation for nearly any language, and if not, well, the spec is 6 pages long ... &lt;img src=&quot;/themes/default/smilies/smile.png&quot; alt=&quot;:)&quot; class=&quot;smiley&quot; /&gt;&lt;/p&gt;</description>
  </item>
      
    
    <item>
    <title>Go API with Gandi! - Jonas B.</title>
    <link>http://www.gandibar.net/post/2007/01/18/Go-API-with-Gandi#c68508</link>
    <guid isPermaLink="false">urn:md5:cb3201d42e0054be423405c47e103512</guid>
    <pubDate>Mon, 19 Feb 2007 11:59:29 +0100</pubDate>
    <dc:creator>Jonas B.</dc:creator>
    
    <description>&lt;p&gt;I would like to know how your protocol compares to EPP and why you chose to go with your own instead of the 'standard'? I know it sometimes assumes an RR model but I see no reason it shouldn't work with resellers as well. It would surely make things easier as there may already be software developed for EPP.&lt;/p&gt;</description>
  </item>
      
</channel>
</rss>