<?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"
	>
<channel>
	<title>Comments on: Answers for Sergey</title>
	<atom:link href="http://steve.vinoski.net/blog/2007/11/17/answers-for-sergey/feed/" rel="self" type="application/rss+xml" />
	<link>http://steve.vinoski.net/blog/2007/11/17/answers-for-sergey/</link>
	<description>Ask forgiveness, not permission.</description>
	<pubDate>Sun, 07 Sep 2008 17:33:03 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.1</generator>
		<item>
		<title>By: REST vs. WS-* &#8230; Does it help me to achieve my goal? &#171; Zettelkasten</title>
		<link>http://steve.vinoski.net/blog/2007/11/17/answers-for-sergey/#comment-789</link>
		<dc:creator>REST vs. WS-* &#8230; Does it help me to achieve my goal? &#171; Zettelkasten</dc:creator>
		<pubDate>Mon, 31 Mar 2008 19:22:39 +0000</pubDate>
		<guid isPermaLink="false">http://steve.vinoski.net/blog/2007/11/17/answers-for-sergey/#comment-789</guid>
		<description>[...] of the REST approach consider using HTTP as a mere transport as abusive (e.g. Tilkov, Vinovsky). For me, using a word like &#8220;abuse&#8221; sounds like putting HTTP on a throne. You have to [...]</description>
		<content:encoded><![CDATA[<p>[...] of the REST approach consider using HTTP as a mere transport as abusive (e.g. Tilkov, Vinovsky). For me, using a word like &#8220;abuse&#8221; sounds like putting HTTP on a throne. You have to [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Service-Oriented Architecture mobile edition</title>
		<link>http://steve.vinoski.net/blog/2007/11/17/answers-for-sergey/#comment-343</link>
		<dc:creator>Service-Oriented Architecture mobile edition</dc:creator>
		<pubDate>Sat, 01 Dec 2007 17:07:12 +0000</pubDate>
		<guid isPermaLink="false">http://steve.vinoski.net/blog/2007/11/17/answers-for-sergey/#comment-343</guid>
		<description>[...] are now wondering out loud if this is the way things are heading. James Snell, Dare Obasanjo, Steve Vinoski, and Sergey Beryozkin (and several others) have been engaged in a running online debate about the [...]</description>
		<content:encoded><![CDATA[<p>[...] are now wondering out loud if this is the way things are heading. James Snell, Dare Obasanjo, Steve Vinoski, and Sergey Beryozkin (and several others) have been engaged in a running online debate about the [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Paul Sandoz</title>
		<link>http://steve.vinoski.net/blog/2007/11/17/answers-for-sergey/#comment-289</link>
		<dc:creator>Paul Sandoz</dc:creator>
		<pubDate>Mon, 19 Nov 2007 15:25:58 +0000</pubDate>
		<guid isPermaLink="false">http://steve.vinoski.net/blog/2007/11/17/answers-for-sergey/#comment-289</guid>
		<description>Regarding your answer to question #2: "If code generation is acceptable, would you welcome WADL? If yes, what to do with generated client types with respect to the change management ?"

WADL can be useful to document services:

http://www.mnot.net/blog/2005/05/18/WADL

WADL can represent meta-data, as hypermedia, of a resource that is lacking when using the 'raw' HTTP OPTIONS method.</description>
		<content:encoded><![CDATA[<p>Regarding your answer to question #2: &#8220;If code generation is acceptable, would you welcome WADL? If yes, what to do with generated client types with respect to the change management ?&#8221;</p>
<p>WADL can be useful to document services:</p>
<p><a href="http://www.mnot.net/blog/2005/05/18/WADL" rel="nofollow">http://www.mnot.net/blog/2005/05/18/WADL</a></p>
<p>WADL can represent meta-data, as hypermedia, of a resource that is lacking when using the &#8216;raw&#8217; HTTP OPTIONS method.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dare Obasanjo aka Carnage4Life - What's Right and Wrong with Code Generation in Web Services</title>
		<link>http://steve.vinoski.net/blog/2007/11/17/answers-for-sergey/#comment-288</link>
		<dc:creator>Dare Obasanjo aka Carnage4Life - What's Right and Wrong with Code Generation in Web Services</dc:creator>
		<pubDate>Mon, 19 Nov 2007 15:22:08 +0000</pubDate>
		<guid isPermaLink="false">http://steve.vinoski.net/blog/2007/11/17/answers-for-sergey/#comment-288</guid>
		<description>[...] Steve Vinoski's Answers for Sergey I stumbled upon Sergey Beryozkin's Questions for Steve&#160;which started of with the following [...]</description>
		<content:encoded><![CDATA[<p>[...] Steve Vinoski&#8217;s Answers for Sergey I stumbled upon Sergey Beryozkin&#8217;s Questions for Steve&nbsp;which started of with the following [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Pete Lacey</title>
		<link>http://steve.vinoski.net/blog/2007/11/17/answers-for-sergey/#comment-287</link>
		<dc:creator>Pete Lacey</dc:creator>
		<pubDate>Mon, 19 Nov 2007 12:02:52 +0000</pubDate>
		<guid isPermaLink="false">http://steve.vinoski.net/blog/2007/11/17/answers-for-sergey/#comment-287</guid>
		<description>Regarding question #4: "Would you expect in the future even software modules interacting with each other through a common generic interfaces?"  

You might want to take a look at NetKernel (http://1060.org/).  I haven't used it personally, but the 1060 folks gave me a briefing.  And from what they told me, long ago they independently derived the RESTful principles of the Web (uniform interdace, caching, etc.) and boiled them down into the innards of a single application server.  From perusing their mailing lists, however, it seems they haven't fully embraced HTTP.  Presumably, that'll be in some future release.</description>
		<content:encoded><![CDATA[<p>Regarding question #4: &#8220;Would you expect in the future even software modules interacting with each other through a common generic interfaces?&#8221;  </p>
<p>You might want to take a look at NetKernel (http://1060.org/).  I haven&#8217;t used it personally, but the 1060 folks gave me a briefing.  And from what they told me, long ago they independently derived the RESTful principles of the Web (uniform interdace, caching, etc.) and boiled them down into the innards of a single application server.  From perusing their mailing lists, however, it seems they haven&#8217;t fully embraced HTTP.  Presumably, that&#8217;ll be in some future release.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
