<?xml version="1.0" encoding="UTF-8"?> <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/" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:sy="http://purl.org/rss/1.0/modules/syndication/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" ><channel><title>American Butifarra &#187; Protocol</title> <atom:link href="http://claude.betancourt.us/topic/protocol/feed/" rel="self" type="application/rss+xml" /><link>http://claude.betancourt.us</link> <description>Claude Betancourt&#039;s Personal Blog</description> <lastBuildDate>Fri, 16 Dec 2011 02:43:25 +0000</lastBuildDate> <language>en</language> <sy:updatePeriod>hourly</sy:updatePeriod> <sy:updateFrequency>1</sy:updateFrequency> <generator>http://wordpress.org/?v=3.3.1</generator> <item><title>Introduction to Ext.Direct</title><link>http://claude.betancourt.us/introduction-to-extdirect/</link> <comments>http://claude.betancourt.us/introduction-to-extdirect/#comments</comments> <pubDate>Wed, 13 May 2009 14:09:52 +0000</pubDate> <dc:creator>Claude</dc:creator> <category><![CDATA[Articles]]></category> <category><![CDATA[Ext JS]]></category> <category><![CDATA[Framework]]></category> <category><![CDATA[JavaScript]]></category> <category><![CDATA[Platform]]></category> <category><![CDATA[Protocol]]></category> <category><![CDATA[.NET]]></category> <category><![CDATA[ColdFusion]]></category> <category><![CDATA[Java]]></category> <category><![CDATA[Library]]></category> <category><![CDATA[Perl]]></category> <category><![CDATA[PHP]]></category> <category><![CDATA[Ruby]]></category><guid isPermaLink="false">http://claude.betancourt.us/?p=581</guid> <description><![CDATA[Evan Trimboli of the Ext-JS team just published an article describing Ext.Direct, a remoting API that is part of Ext 3.0. <a href="http://claude.betancourt.us/introduction-to-extdirect/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description> <content:encoded><![CDATA[<p><span class="drop_cap">E</span>van Trimboli of the Ext-JS team just published an article describing Ext.Direct, a remoting API that is part of Ext 3.0. The team has created a <a href="http://extjs.com/products/extjs/direct.php">remoting specification</a> that you can use to implement the server-side stack of your choice.</p><p>Details about server-specific implementations already being maintained <a href="http://extjs.com/forum/showthread.php?t=67992">can be found here</a>.</p><blockquote><p> Ext.Direct is a new package in Ext JS 3.0 that helps alleviate many of these issues by streamlining communication between your client and server. When using Ext.Direct, you can expect to write 30% less code by eliminating common boiler plate code.</p><p>The Ext.direct namespace introduces several new classes for a close integration with the server-side. New classes have also been added to the Ext.data namespace for working with Ext.data.Stores which are backed by data from an Ext.Direct method.</p><p>Ext.Direct uses a provider architecture, where one or more providers are used to transport data to and from the server. There are several providers that exist in the core at the moment, for example a JsonProvider for simple JSON operations and a PollingProvider for repeated requests. One of the most powerful providers is the RemotingProvider.</p></blockquote><p><a href="http://extjs.com/blog/2009/05/13/introducing-ext-direct/">Read the rest here</a>.</p> ]]></content:encoded> <wfw:commentRss>http://claude.betancourt.us/introduction-to-extdirect/feed/</wfw:commentRss> <slash:comments>0</slash:comments> </item> <item><title>Force a URL to Use HTTPS</title><link>http://claude.betancourt.us/how-to-force-a-url-to-use-https/</link> <comments>http://claude.betancourt.us/how-to-force-a-url-to-use-https/#comments</comments> <pubDate>Sat, 28 Feb 2009 03:02:55 +0000</pubDate> <dc:creator>Claude</dc:creator> <category><![CDATA[How-To]]></category> <category><![CDATA[Protocol]]></category> <category><![CDATA[Security]]></category> <category><![CDATA[Apache]]></category> <category><![CDATA[ColdFusion]]></category> <category><![CDATA[IIS]]></category> <category><![CDATA[MachII]]></category> <category><![CDATA[plugin]]></category> <category><![CDATA[Rewrite]]></category><guid isPermaLink="false">http://claude.betancourt.us/?p=385</guid> <description><![CDATA[Site owners sometimes need to make sure secure connections are used. They can do this quickly with this Apache rule. <a href="http://claude.betancourt.us/how-to-force-a-url-to-use-https/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description> <content:encoded><![CDATA[<p><span class="drop_cap">T</span>oday I came across some old ColdFusion <span class="amp">&#038;</span> Mach-II (1.0) code where a plugin was used to force HTTPS. I assume the original developer decided to go with this solution because the target environment was Windows and Internet Information Server.</p><p>The task becomes a lot easier under Apache. So I threw away the plugin code and added the following rule to the Apache configuration:</p><pre class="brush: xml; title: ; notranslate">
&lt;directory &quot;/public_html/mysite.com&quot;&gt;
RewriteEngine on
RewriteCond %{HTTPS} !=on
RewriteRule ^(.*) https://%{HTTP_HOST}/$1	[R,L]
&lt;/directory&gt;
</pre><p class="alert">The directive above can be placed inside a <span class="amp">VirtualHost</span> or <span class="amp">Directory</span> directives, but this usually requires access to the Apache server configuration, which is not typically possible in a shared hosting environment &#8212; in that case, the rule can be added to the <span class="amp">.htaccess</span> file.</p><p>Alternatively we could have used the <a href="http://httpd.apache.org/docs/2.2/mod/mod_ssl.html#sslrequiressl">SSLRequireSSL Apache (2.x) directive</a>, but this would only block access to the non HTTPS address. In our case we want to automatically redirect the users instead of displaying an error message.</p> ]]></content:encoded> <wfw:commentRss>http://claude.betancourt.us/how-to-force-a-url-to-use-https/feed/</wfw:commentRss> <slash:comments>2</slash:comments> </item> <item><title>BlazeDS: Flex Data Services Goes Open-Source</title><link>http://claude.betancourt.us/blaxeds-flex-data-services-to-go-open-source/</link> <comments>http://claude.betancourt.us/blaxeds-flex-data-services-to-go-open-source/#comments</comments> <pubDate>Thu, 13 Dec 2007 11:33:45 +0000</pubDate> <dc:creator>Claude</dc:creator> <category><![CDATA[Protocol]]></category> <category><![CDATA[ColdFusion]]></category> <category><![CDATA[Flash]]></category> <category><![CDATA[Flex]]></category><guid isPermaLink="false">http://claude.betancourt.us/blog/?p=111</guid> <description><![CDATA[So far the standard way of making data connections in Ajax applications has been over XmlHttpRequest, which requires clients to constantly poll backend servers. Adobe is taking advantage of the opportunity to open up a solid platform capable of providing &#8230; <a href="http://claude.betancourt.us/blaxeds-flex-data-services-to-go-open-source/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description> <content:encoded><![CDATA[<p><span class="drop_cap">S</span>o far the standard way of making data connections in Ajax applications has been over XmlHttpRequest, which requires clients to constantly poll backend servers.  Adobe is taking advantage of the opportunity to open up a solid platform capable of providing persistent connections (<a href="http://en.wikipedia.org/wiki/Push_technology">server push</a> / <a href="http://en.wikipedia.org/wiki/Comet_%28programming%29">Comet</a>) and the AMF specification.</p><p><a href="http://labs.adobe.com/technologies/blazeds/">According to the Adobe Labs site</a>:</p><blockquote><p>Adobe is announcing plans to release source code for its server side remoting and messaging technologies under a new open source product named BlazeDS. Now, developers can easily connect to back-end distributed data and push data in real-time to AdobeÂ® Flexâ„¢ and AdobeÂ® Integrated Runtime (AIR) applications for more responsive rich Internet application (RIA) experiences. Previously available only as part of Adobe LiveCycleÂ® Data Services ES software, the technologies included in BlazeDS, along with the Action Message Format (AMF) protocol specification, are being contributed to open source under the Lesser General Public License (LGPL v3) and are available immediately as public betas on Adobe Labs.</p></blockquote> ]]></content:encoded> <wfw:commentRss>http://claude.betancourt.us/blaxeds-flex-data-services-to-go-open-source/feed/</wfw:commentRss> <slash:comments>0</slash:comments> </item> <item><title>HTTP Streaming and Internet Explorer</title><link>http://claude.betancourt.us/http-streaming-and-internet-explorer/</link> <comments>http://claude.betancourt.us/http-streaming-and-internet-explorer/#comments</comments> <pubDate>Thu, 08 Nov 2007 05:26:23 +0000</pubDate> <dc:creator>Claude</dc:creator> <category><![CDATA[Protocol]]></category> <category><![CDATA[Comet]]></category> <category><![CDATA[Streaming]]></category> <category><![CDATA[XHR]]></category><guid isPermaLink="false">http://claude.betancourt.us/blog/?p=107</guid> <description><![CDATA[According to Michael Carter, of Comet Daily, evidence of a surefire way to use Comet with IE is purely anecdotal. He describes the steps he followed to uncover the cause of dropped connections in his ActiveX htmlfile hack and how &#8230; <a href="http://claude.betancourt.us/http-streaming-and-internet-explorer/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description> <content:encoded><![CDATA[<p><span class="drop_cap">A</span>ccording to <a href="http://cometdaily.com/people/michael_carter"><span style="font-weight: bold">Michael Carter</span></a>, of Comet Daily, evidence of a surefire way to use Comet with IE is purely anecdotal.  He describes the steps he followed to uncover the cause of dropped connections in his <a href="http://msdn2.microsoft.com/en-us/library/aa752574.aspx"><span style="font-weight: bold">ActiveX htmlfile</span></a> hack and how to elegantly work around the issue.</p><p><a href="http://cometdaily.com/2007/10/25/http-streaming-and-internet-explorer/"><span style="font-weight: bold">Read the whole story here&#8230;</span></a></p><p style="text-align: right; font-size: 8px">Blogged with <a href="http://www.flock.com/blogged-with-flock" title="Flock" target="_new">Flock</a></p><p></p><p style="font-size: 10px; text-align: right">Tags: <a href="http://technorati.com/tag/comet" rel="tag">comet</a>, <a href="http://technorati.com/tag/javascript" rel="tag">javascript</a>, <a href="http://technorati.com/tag/%20ie" rel="tag"> ie</a>, <a href="http://technorati.com/tag/%20iframe" rel="tag"> iframe</a>, <a href="http://technorati.com/tag/%20hack" rel="tag"> hack</a></p><p></p> ]]></content:encoded> <wfw:commentRss>http://claude.betancourt.us/http-streaming-and-internet-explorer/feed/</wfw:commentRss> <slash:comments>0</slash:comments> </item> <item><title>From DHTML to DOM Scripting</title><link>http://claude.betancourt.us/from-dhtml-to-dom-scripting/</link> <comments>http://claude.betancourt.us/from-dhtml-to-dom-scripting/#comments</comments> <pubDate>Tue, 11 Apr 2006 15:10:52 +0000</pubDate> <dc:creator>Claude</dc:creator> <category><![CDATA[JavaScript]]></category> <category><![CDATA[Protocol]]></category><guid isPermaLink="false">http://claude.betancourt.us/blog/?p=40</guid> <description><![CDATA[Here is a good article by Chris Heilmann for those of you making a move to new JavaScript coding styles and frameworks.]]></description> <content:encoded><![CDATA[<p>Here is a <a href="http://icant.co.uk/articles/from-dhtml-to-dom/" title="From DHTML to DOM Scripting" target="_blank"><b>good article</b></a> by Chris Heilmann for those of you making a move to new JavaScript coding styles and frameworks.</p> ]]></content:encoded> <wfw:commentRss>http://claude.betancourt.us/from-dhtml-to-dom-scripting/feed/</wfw:commentRss> <slash:comments>0</slash:comments> </item> <item><title>Excellent Addition to Prototype.js</title><link>http://claude.betancourt.us/excellent-addition-to-prototypejs/</link> <comments>http://claude.betancourt.us/excellent-addition-to-prototypejs/#comments</comments> <pubDate>Thu, 30 Mar 2006 14:25:43 +0000</pubDate> <dc:creator>Claude</dc:creator> <category><![CDATA[Protocol]]></category><guid isPermaLink="false">http://claude.betancourt.us/blog/?p=39</guid> <description><![CDATA[$E() is for those of us who use the prototype framework, and have written additional functions to manage new elements and their contents.]]></description> <content:encoded><![CDATA[<p><b><a href="http://www.arantius.com/article/dollar-e" title="Dollar E()" target="_blank">$E()</a></b> is for those of us who use the <a href="http://prototype.conio.net/" title="Prototype JavaScript Framework" target="_blank">prototype framework</a>, and have written additional functions to manage new elements and their contents.</p> ]]></content:encoded> <wfw:commentRss>http://claude.betancourt.us/excellent-addition-to-prototypejs/feed/</wfw:commentRss> <slash:comments>0</slash:comments> </item> <item><title>CFHTTP Trouble: Connecting to Web Services that Use GZip Compression</title><link>http://claude.betancourt.us/cfhttp-trouble-connecting-to-web-services-that-use-gzip-compression/</link> <comments>http://claude.betancourt.us/cfhttp-trouble-connecting-to-web-services-that-use-gzip-compression/#comments</comments> <pubDate>Sat, 31 Dec 2005 00:29:00 +0000</pubDate> <dc:creator>Claude</dc:creator> <category><![CDATA[Protocol]]></category> <category><![CDATA[Tutorials]]></category> <category><![CDATA[ColdFusion]]></category><guid isPermaLink="false">http://claude.betancourt.us/blog/?p=36</guid> <description><![CDATA[Rob Gonda posted this today, which I had also experienced while attempting to connect to the Yahoo! Maps API. The solution in my case was to add charset=&#8221;utf-8&#8243; to the cfhttp call.]]></description> <content:encoded><![CDATA[<p>Rob Gonda <a href="http://www.robgonda.com/blog/index.cfm/2005/12/30/cfhttp-and-gzip-compression">posted this today</a>, which I had also experienced while attempting to connect to the Yahoo! Maps API.</p><p>The solution in my case was to add charset=&#8221;utf-8&#8243; to the cfhttp call.</p> ]]></content:encoded> <wfw:commentRss>http://claude.betancourt.us/cfhttp-trouble-connecting-to-web-services-that-use-gzip-compression/feed/</wfw:commentRss> <slash:comments>0</slash:comments> </item> </channel> </rss>
<!-- Served from: claude.betancourt.us @ 2012-02-07 14:59:49 by W3 Total Cache -->
