<?xml version="1.0" encoding="UTF-8"?>
<!-- generator="wordpress/2.8.4" -->
<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>http://blog.sLajax.com</title>
	<link>http://blog.slajax.com</link>
	<description>secure lightweight ajax solutions</description>
	<pubDate>Wed, 16 Dec 2009 07:39:40 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<language>en</language>
			<item>
		<title>Javascript Cross Domain Ajax</title>
		<link>http://blog.slajax.com/2008/07/23/javascript-cross-domain-ajax/</link>
        <customfield>dojo.png</customfield>
		<comments>http://blog.slajax.com/2008/07/23/javascript-cross-domain-ajax/#comments</comments>
		<pubDate>Wed, 23 Jul 2008 17:16:23 +0000</pubDate>
		<dc:creator>Kyle</dc:creator>
				<category><![CDATA[api]]></category>
		<category><![CDATA[blast radius]]></category>
		<category><![CDATA[frameworks]]></category>
		<category><![CDATA[javascript]]></category>
		<category><![CDATA[crossdomain]]></category>
		<category><![CDATA[http]]></category>
		<category><![CDATA[mashup]]></category>
		<category><![CDATA[x-domain]]></category>

		<guid isPermaLink="false">http://blog.slajax.com/?p=32</guid>
		<description><![CDATA[Since I joined Blast Radius [1] I have been introduced to a lot of new and interesting development practices, frameworks and designs that I have always read or heard about, but was never really forced or motivated to imply in my daily progression.
One such framework I wrote briefly about is Mojo [2]. Being a framework that has evolved from the Dojo Toolkit [3] my interest peaked this morning when I read a very interesting article on Ajaxian [4] about cross domain transport.


Originally as more of a low level technologist who only picked up ajax and interface development as a smooth view state for communicating with my middle tier controllers I found Javascript to be very much lacking the web services department. Very often the techniques that have been traditionally used consist of one of two strategies for x-domain communication;

1- A remote javascript include is served using:



[1] http://blog.slajax.com/2008/06/17/relocating-to-vancouver-senior-interface-developer/
[2] http://blog.slajax.com/2008/07/17/first-week-at-blast-radius-over/
[3] http://dojotoolkit.com
[4] http://ajaxian.com/archives/windowname-meet-dojoxiowindowname]]></description>
			<content:encoded><![CDATA[Since I <a href="http://blog.slajax.com/2008/06/17/relocating-to-vancouver-senior-interface-developer/" target="_blank">joined Blast Radius</a> I have been introduced to a lot of new and interesting development practices, frameworks and designs that I have always read or heard about, but was never really forced or motivated to imply in my daily progression.
One such framework I wrote briefly about is <a href="http://blog.slajax.com/2008/07/17/first-week-at-blast-radius-over/"  target="_blank">Mojo</a>. Being a framework that has evolved from the <a href="http://dojotoolkit.com"  target="_blank">Dojo Toolkit</a> my interest peaked this morning when I read a very interesting article on <a href="http://ajaxian.com/archives/windowname-meet-dojoxiowindowname" target="_blank">Ajaxian</a> about cross domain transport.
<br/><br/>

Originally as more of a low level technologist who only picked up ajax and interface development as a smooth view state for communicating with my middle tier controllers I found Javascript to be very much lacking the web services department. Very often the techniques that have been traditionally used consist of one of two strategies for x-domain communication;
<br/><br/>
1- <strong>A remote javascript include is served using:</strong><br/>
<div class='codeWrapper'><div class='codeTitle'>javascript<span class='codeInstruct'>hover edges to scroll</span></div><code><pre>&nbsp;
&lt;script type=<span style="color: #3366CC;">'text/javascript href='</span>http:<span style="color: #009900; font-style: italic;">//remotehost/js/api.js?param=1&amp;param2'&gt;</span></pre></code></div>
This is usually a server side script that generates the file contents based on the parameters, and then either renders content locally into your DOM, or provides you with a set of methods that will allow you to manipulate the content. This is not a very secure model and does not allow you to interact with raw xml data very robustly, but as long as you trust the source that is rending the content, it is quite efficient.
<br/><br/>
2- <strong>By matter of Proxy.</strong><br/>
This method I&#8217;ve used very often for direct communication with XML, SOAP, or REST gateways. Generally, I will develop the interface layer to communicate with a server side controller which will then use Curl to invoke the remote data, process and return as an JSON object. I find this method to be very robust, and allows you to create a very extensible gateway for your Javascript cross domain requests.
<br/><br/>

With that said, the post I read this morning is indicating that a new methodology for cross-domain scripting is emerging in the Dojo framework. By way of the property <i>window.name</i> one can make a remote request and retrieve data without exploiting the ever so wonderful cross domain security model that we are subject to in all our favorite browsers. This concept is very new but interesting. It opens up a whole new world of client side mash-up possibilities that are sure to get the creative juices flowing in the client side development space. Here is an example of it would be implemented:

<div class='codeWrapper'><div class='codeTitle'>javascript<span class='codeInstruct'>hover edges to scroll</span></div><code><pre>&nbsp;
dojox.<span style="color: #006600;">io</span>.<span style="color: #006600;">windowName</span>.<span style="color: #006600;">send</span><span style="color: #66cc66;">&#40;</span>method, args<span style="color: #66cc66;">&#41;</span>; <span style="color: #009900; font-style: italic;">// simple method</span>
<span style="color: #009900; font-style: italic;">// deferred result</span>
&nbsp;
<span style="color: #003366; font-weight: bold;">var</span> deferred = dojox.<span style="color: #006600;">io</span>.<span style="color: #006600;">windowName</span>.<span style="color: #006600;">send</span><span style="color: #66cc66;">&#40;</span><span style="color: #3366CC;">"GET"</span>, <span style="color: #66cc66;">&#123;</span>url:<span style="color: #3366CC;">"http://somesite.com/resource"</span><span style="color: #66cc66;">&#125;</span><span style="color: #66cc66;">&#41;</span>;
deferred.<span style="color: #006600;">addCallback</span><span style="color: #66cc66;">&#40;</span><span style="color: #003366; font-weight: bold;">function</span><span style="color: #66cc66;">&#40;</span>result<span style="color: #66cc66;">&#41;</span><span style="color: #66cc66;">&#123;</span>
  <span style="color: #000066;">alert</span><span style="color: #66cc66;">&#40;</span><span style="color: #3366CC;">"The request returned "</span> + result<span style="color: #66cc66;">&#41;</span>;
<span style="color: #66cc66;">&#125;</span><span style="color: #66cc66;">&#41;</span>;</pre></code></div>


]]></content:encoded>
			<wfw:commentRss>http://blog.slajax.com/2008/07/23/javascript-cross-domain-ajax/feed/</wfw:commentRss>
		</item>
		<item>
		<title>Open Social is finally here.</title>
		<link>http://blog.slajax.com/2007/11/09/open-social-is-finally-here/</link>
        <customfield>opensocial.jpg</customfield>
		<comments>http://blog.slajax.com/2007/11/09/open-social-is-finally-here/#comments</comments>
		<pubDate>Fri, 09 Nov 2007 19:49:17 +0000</pubDate>
		<dc:creator>Kyle</dc:creator>
				<category><![CDATA[api]]></category>
		<category><![CDATA[frameworks]]></category>
		<category><![CDATA[social networking]]></category>

		<guid isPermaLink="false">http://blog.slajax.com/2007/11/09/open-social-is-finally-here/</guid>
		<description><![CDATA[

So finally the powers that be [1] have chosen to use their voice [2] in an attempt to show the world what "open" really is. We've seen a lot of improvement in the social networking field over the last 2 years, with leadsers such as Linked In [3] and Sales Force [4] showing the world that social networking is not just for weirdos [5].

On Friday, November 02, 2007 at 1:15:00 AM [6] Google posted that Open Social is being lunched with this list of partners [7]. This is a huge step in the right direction for social networking and the internet in general. Now we can all play happily together while Facebook takes the ball and goes home.





[1] http://google.com
[2] http://code.google.com/apis/opensocial/
[3] http://linkedin.com
[4] http://salesforce.com
[5] http://www.encyclopediaofstupid.com/stupid/index.php/Myspace
[6] http://opensocialapis.blogspot.com/2007/11/web-is-better-when-its-social.html
[7] http://code.google.com/apis/opensocial/partners.html]]></description>
			<content:encoded><![CDATA[<img src="http://blog.slajax.com/wp-content/images/opensocial.jpg" alt="open social" />

So finally the <a href="http://google.com" target="_blank">powers that be</a> have chosen to use <a href="http://code.google.com/apis/opensocial/" target="_blank">their voice</a> in an attempt to show the world what &#8220;open&#8221; really is. We&#8217;ve seen a lot of improvement in the social networking field over the last 2 years, with leadsers such as <a href="http://linkedin.com" target="_blank">Linked In</a> and <a href="http://salesforce.com">Sales Force</a> showing the world that social networking is not just for <a href="http://www.encyclopediaofstupid.com/stupid/index.php/Myspace" target="_blank">weirdos</a>.

On <a href="http://opensocialapis.blogspot.com/2007/11/web-is-better-when-its-social.html" target="_blank">Friday, November 02, 2007 at 1:15:00 AM</a> Google posted that Open Social is being lunched with <a href="http://code.google.com/apis/opensocial/partners.html">this list of partners</a>. This is a huge step in the right direction for social networking and the internet in general. Now we can all play happily together while Facebook takes the ball and goes home.



]]></content:encoded>
			<wfw:commentRss>http://blog.slajax.com/2007/11/09/open-social-is-finally-here/feed/</wfw:commentRss>
		</item>
		<item>
		<title>Akelos &#8211; a pragmatic php framework</title>
		<link>http://blog.slajax.com/2007/08/24/akelos-a-pragmatic-php-framework/</link>
        <customfield>akelos.gif</customfield>
		<comments>http://blog.slajax.com/2007/08/24/akelos-a-pragmatic-php-framework/#comments</comments>
		<pubDate>Fri, 24 Aug 2007 21:34:08 +0000</pubDate>
		<dc:creator>Kyle</dc:creator>
				<category><![CDATA[frameworks]]></category>
		<category><![CDATA[php]]></category>
		<category><![CDATA[agile]]></category>
		<category><![CDATA[akelos]]></category>
		<category><![CDATA[framework]]></category>
		<category><![CDATA[pragmatic]]></category>
		<category><![CDATA[rails]]></category>

		<guid isPermaLink="false">http://blog.slajax.com/2007/08/24/akelos-a-pragmatic-php-framework/</guid>
		<description><![CDATA[ [1]



I have recently discovered Akelos [2] a wonderfully efficient framework that allows you to control scaffolding and generate controllers in much the same way that you would in Ruby on Rails. Not only is the framework designed to cut corners, but it also has an amazingly useful version control system, that allows you to upgrade your applications without having to worry about new data impacting crashing the application. 



From my short experience with this software, I can see that it is going to be a very strong favorite in the open source world, in my opinion surpassing it's rival Symfony [3]. I am sure to make this framework an avid part of my tool box and do what I can to promote such a well structured software. Kudos to Bermi over at http://akelos.org [4]






[1] http://akelos.org
[2] http://akelos.org
[3] http://symfony-project.org
[4] http://akelos.org]]></description>
			<content:encoded><![CDATA[<center><a href="http://akelos.org" target="_blank"><img src="/wp-content/images/akelos_logo.jpg" border="0" /></a></center>

<br /><br />

I have recently discovered <a href="http://akelos.org" target="_blank">Akelos</a> a wonderfully efficient framework that allows you to control scaffolding and generate controllers in much the same way that you would in Ruby on Rails. Not only is the framework designed to cut corners, but it also has an amazingly useful version control system, that allows you to upgrade your applications without having to worry about new data impacting crashing the application. 

<br /><br />

From my short experience with this software, I can see that it is going to be a very strong favorite in the open source world, in my opinion surpassing it&#8217;s rival <a href="http://symfony-project.org" target="_blank" />Symfony</a>. I am sure to make this framework an avid part of my tool box and do what I can to promote such a well structured software. Kudos to Bermi over at <a href="http://akelos.org" target="_blank">http://akelos.org</a>


<br /><br />

]]></content:encoded>
			<wfw:commentRss>http://blog.slajax.com/2007/08/24/akelos-a-pragmatic-php-framework/feed/</wfw:commentRss>
		</item>
	</channel>
</rss>
