<?xml version="1.0" encoding="UTF-8"?>
<!-- generator="wordpress/2.2.2" -->
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	>

<channel>
	<title>Quick off the Mark</title>
	<link>http://markthomas.org</link>
	<description>thoughts.collect{ &#124;thought&#124; thought.to_blog }</description>
	<pubDate>Thu, 08 May 2008 02:29:40 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.2.2</generator>
	<language>en</language>
			<item>
		<title>Enhancing WWW::Mechanize</title>
		<link>http://markthomas.org/2008/05/07/enhancing-wwwmechanize/</link>
		<comments>http://markthomas.org/2008/05/07/enhancing-wwwmechanize/#comments</comments>
		<pubDate>Thu, 08 May 2008 02:16:38 +0000</pubDate>
		<dc:creator>Mark Thomas</dc:creator>
		
		<category><![CDATA[Ruby]]></category>

		<guid isPermaLink="false">http://markthomas.org/2008/05/07/enhancing-wwwmechanize/</guid>
		<description><![CDATA[Today I wanted to extract a report from a search appliance. This task involved logging in to the appliance, receiving a cookie, and following a few links. No problem with Mechanize, right?
agent = WWW::Mechanize.new
login_form = agent.get&#40;THUNDERSTONE_URL&#41;.forms.first
login_form.set_fields&#40;:iname =&#62; LOGIN, :ipass =&#62; PASSWORD&#41;
page = agent.submit&#40;login&#41;
page = agent.click page.links.text&#40;PROFILE_NAME&#41;
errors = agent.get_file &#34;#{page.uri}/tsverrors.csv&#34;
Only it turned out that it wasn't [...]]]></description>
			<content:encoded><![CDATA[<p>Today I wanted to extract a report from a search appliance. This task involved logging in to the appliance, receiving a cookie, and following a few links. No problem with Mechanize, right?</p>
<pre class="ruby">agent = WWW::Mechanize.<span style="color:#9900CC;">new</span>
login_form = agent.<span style="color:#9900CC;">get</span><span style="color:#006600; font-weight:bold;">&#40;</span>THUNDERSTONE_URL<span style="color:#006600; font-weight:bold;">&#41;</span>.<span style="color:#9900CC;">forms</span>.<span style="color:#9900CC;">first</span>
login_form.<span style="color:#9900CC;">set_fields</span><span style="color:#006600; font-weight:bold;">&#40;</span>:iname =&gt; LOGIN, :ipass =&gt; PASSWORD<span style="color:#006600; font-weight:bold;">&#41;</span>
page = agent.<span style="color:#9900CC;">submit</span><span style="color:#006600; font-weight:bold;">&#40;</span>login<span style="color:#006600; font-weight:bold;">&#41;</span>
page = agent.<span style="color:#9900CC;">click</span> page.<span style="color:#9900CC;">links</span>.<span style="color:#9900CC;">text</span><span style="color:#006600; font-weight:bold;">&#40;</span>PROFILE_NAME<span style="color:#006600; font-weight:bold;">&#41;</span>
errors = agent.<span style="color:#9900CC;">get_file</span> <span style="color:#996600;">&quot;#{page.uri}/tsverrors.csv&quot;</span></pre>
<p>Only it turned out that it wasn't receiving the cookie.  <a href="http://markthomas.org/2008/05/07/enhancing-wwwmechanize/#more-13" class="more-link">(more...)</a></p>
]]></content:encoded>
			<wfw:commentRss>http://markthomas.org/2008/05/07/enhancing-wwwmechanize/feed/</wfw:commentRss>
		</item>
		<item>
		<title>Language comparisons are usually flawed</title>
		<link>http://markthomas.org/2008/02/16/language-comparisons-are-always-flawed/</link>
		<comments>http://markthomas.org/2008/02/16/language-comparisons-are-always-flawed/#comments</comments>
		<pubDate>Sat, 16 Feb 2008 05:01:11 +0000</pubDate>
		<dc:creator>Mark Thomas</dc:creator>
		
		<category><![CDATA[Python]]></category>

		<category><![CDATA[Rails]]></category>

		<category><![CDATA[Ruby]]></category>

		<guid isPermaLink="false">http://markthomas.org/2008/02/16/language-comparisons-are-always-flawed/</guid>
		<description><![CDATA[There are many blog posts that basically say, "Given problem X, you can solve it elegantly in language Y. Language Y is awesome!" The problem with this is that it is essentially a strawman argument. Who is to say that problem X would even be the same in other languages, if you take their conventions [...]]]></description>
			<content:encoded><![CDATA[<p>There are many blog posts that basically say, "Given problem X, you can solve it elegantly in language Y. Language Y is awesome!" The problem with this is that it is essentially a strawman argument. Who is to say that problem X would even be the same in other languages, if you take their conventions and idioms into account?  <a href="http://markthomas.org/2008/02/16/language-comparisons-are-always-flawed/#more-11" class="more-link">(more...)</a></p>
]]></content:encoded>
			<wfw:commentRss>http://markthomas.org/2008/02/16/language-comparisons-are-always-flawed/feed/</wfw:commentRss>
		</item>
		<item>
		<title>Industrial-strength Web Services for Ruby</title>
		<link>http://markthomas.org/2008/01/14/industrial-strength-web-services-for-ruby/</link>
		<comments>http://markthomas.org/2008/01/14/industrial-strength-web-services-for-ruby/#comments</comments>
		<pubDate>Mon, 14 Jan 2008 16:27:12 +0000</pubDate>
		<dc:creator>Mark Thomas</dc:creator>
		
		<category><![CDATA[Rails]]></category>

		<category><![CDATA[Web Services]]></category>

		<category><![CDATA[Ruby]]></category>

		<guid isPermaLink="false">http://markthomas.org/2008/01/14/industrial-strength-web-services-for-ruby/</guid>
		<description><![CDATA[The folks at WSO2 have created a Ruby binding for their enterprise Web Services stack, WSF/C. WSF/Ruby supports SOAP 1.2 and many WS-* specifications, including WS-Addressing, WS-Security, and WS-Reliable Messaging. Built on Apache Axis2, Rampart, and Sandesha2, it is interoperable with .NET and J2EE SOAP implementations. Now that SOAP has been decoupled from Rails, this [...]]]></description>
			<content:encoded><![CDATA[<p>The folks at <a href="http://wso2.org/">WSO2</a> have created a Ruby binding for their enterprise Web Services stack, WSF/C. <a href="http://wso2.org/projects/wsf/ruby">WSF/Ruby</a> supports SOAP 1.2 and many WS-* specifications, including WS-Addressing, WS-Security, and WS-Reliable Messaging. Built on Apache Axis2, Rampart, and Sandesha2, it is interoperable with .NET and J2EE SOAP implementations. Now that SOAP has been decoupled from Rails, this has potential as a solid replacement.</p>
<p> <a href="http://markthomas.org/2008/01/14/industrial-strength-web-services-for-ruby/#more-10" class="more-link">(more...)</a></p>
]]></content:encoded>
			<wfw:commentRss>http://markthomas.org/2008/01/14/industrial-strength-web-services-for-ruby/feed/</wfw:commentRss>
		</item>
		<item>
		<title>Getting Started with SOAP4R</title>
		<link>http://markthomas.org/2007/09/12/getting-started-with-soap4r/</link>
		<comments>http://markthomas.org/2007/09/12/getting-started-with-soap4r/#comments</comments>
		<pubDate>Thu, 13 Sep 2007 02:35:24 +0000</pubDate>
		<dc:creator>Mark Thomas</dc:creator>
		
		<category><![CDATA[Web Services]]></category>

		<category><![CDATA[Ruby]]></category>

		<guid isPermaLink="false">http://markthomas.org/2007/09/12/getting-started-with-soap4r/</guid>
		<description><![CDATA[SOAP4R is a Ruby library for accessing Web Services via SOAP. Recently I had a chance to explore SOAP4R. Here's how to get started with it.
]]></description>
			<content:encoded><![CDATA[<p>SOAP4R is a Ruby library for accessing Web Services via SOAP. Recently I had a chance to explore SOAP4R. Here's how to get started with it.</p>
<p> <a href="http://markthomas.org/2007/09/12/getting-started-with-soap4r/#more-3" class="more-link">(more...)</a></p>
]]></content:encoded>
			<wfw:commentRss>http://markthomas.org/2007/09/12/getting-started-with-soap4r/feed/</wfw:commentRss>
		</item>
		<item>
		<title>Is SOAP dying?</title>
		<link>http://markthomas.org/2007/09/08/is-soap-dying/</link>
		<comments>http://markthomas.org/2007/09/08/is-soap-dying/#comments</comments>
		<pubDate>Sun, 09 Sep 2007 02:19:28 +0000</pubDate>
		<dc:creator>Mark Thomas</dc:creator>
		
		<category><![CDATA[Web Services]]></category>

		<guid isPermaLink="false">http://markthomas.org/2007/09/08/is-soap-dying/</guid>
		<description><![CDATA[I've been asked a number of times whether SOAP is becoming obsolete. Cited examples:

Amazon offers both SOAP and REST interfaces to its API. According to Amazon, REST was used 85% of the time.
Google quietly dropped its SOAP API in late 2006.
Ruby on Rails 2.0 will drop its SOAP API in favor of a built-in native [...]]]></description>
			<content:encoded><![CDATA[<p>I've been asked a number of times whether SOAP is becoming obsolete. Cited examples:</p>
<ul>
<li>Amazon offers both SOAP and REST interfaces to its API. According to Amazon, <a href="http://www.oreillynet.com/pub/wlg/3005" target="_blank">REST was used 85% of the time</a>.</li>
<li>Google quietly <a href="http://code.google.com/apis/soapsearch/" target="_blank">dropped its SOAP API</a> in late 2006.</li>
<li>Ruby on Rails 2.0 will <a href="http://radar.oreilly.com/archives/2007/05/dhhs_rails_keyn.html" target="_blank">drop its SOAP API</a> in favor of a built-in native REST API.</li>
</ul>
<p>So does this signify the end of SOAP?<br />
 <a href="http://markthomas.org/2007/09/08/is-soap-dying/#more-5" class="more-link">(more...)</a></p>
]]></content:encoded>
			<wfw:commentRss>http://markthomas.org/2007/09/08/is-soap-dying/feed/</wfw:commentRss>
		</item>
	</channel>
</rss>
