<?xml version="1.0" encoding="utf-8"?>
			
			<rss version="2.0">
			<channel>
			<title>Application Generation - AJAX</title>
			<link>http://www.pbell.com/index.cfm</link>
			<description>A series of occasional musings on architecting, securing, optimizing and generating web based applications. By Peter Bell.</description>
			<language>en-us</language>
			<pubDate>Tue, 18 Jun 2013 20:47:27 -0400</pubDate>
			<lastBuildDate>Thu, 13 Sep 2007 15:00:00 -0400</lastBuildDate>
			<generator>BlogCFC</generator>
			<docs>http://blogs.law.harvard.edu/tech/rss</docs>
			<managingEditor>test@test.com</managingEditor>
			<webMaster>test@test.com</webMaster>
			
			
			
			
			
			<item>
				<title>Live (on-Blur) Validation</title>
				<link>http://www.pbell.com/index.cfm/2007/9/13/Live-onBlur-Validation</link>
				<description>
				
				I&apos;m really starting to like the idea of three stage validation, validating on blur where possible, on submit where supported and then of course on the server as a backstop for users without Javascript and/or with malicious intent. There is a &lt;a href=&quot;http://www.livevalidation.com/examples&quot;&gt;framework&lt;/a&gt; designed to make it easy to create on-blur validations and while it isn&apos;t exactly how I want to work, I think it&apos;s close enough that my first jQuery plug-in may well be based on this concept, although with support for a validation to be described once and then run both on blur and on submit.

Thoughts?
				
				</description>
				
				<category>AJAX</category>
				
				<category>JavaScript</category>
				
				<pubDate>Thu, 13 Sep 2007 15:00:00 -0400</pubDate>
				<guid>http://www.pbell.com/index.cfm/2007/9/13/Live-onBlur-Validation</guid>
				
			</item>
			
		 	
			
			
			<item>
				<title>AJAX Prototyping Framework</title>
				<link>http://www.pbell.com/index.cfm/2007/9/11/AJAX-Prototyping-Framework</link>
				<description>
				
				One of the biggest issues with developing sites is finding the most efficient ways of quickly prototyping sites. I just saw a posting about a new &lt;a href=&quot;http://ajaxian.com/archives/protoscript-prototype-web-apps-with-a-json-dsl&quot;&gt;framework&lt;/a&gt; designed to quickly prototype AJAXy effects. The framework really doesn&apos;t quite fit what I&apos;m trying to do, but it&apos;s an interesting approach.
				
				</description>
				
				<category>AJAX</category>
				
				<category>JavaScript</category>
				
				<pubDate>Tue, 11 Sep 2007 15:00:00 -0400</pubDate>
				<guid>http://www.pbell.com/index.cfm/2007/9/11/AJAX-Prototyping-Framework</guid>
				
			</item>
			
		 	
			
			
			<item>
				<title>Javascript Highjacking Risk for AJAX Apps?</title>
				<link>http://www.pbell.com/index.cfm/2007/4/2/Javascript-Highjacking-Risk-for-AJAX-Apps</link>
				<description>
				
				I *still* haven&apos;t had a moment to fire up JQuery, but &lt;a href=&quot;http://www.cbronline.com/article_news.asp?guid=484BC88B-630F-4E74-94E9-8D89DD0E6606&quot;&gt;this looks like something to check&lt;/a&gt; with the AJAX framework guys to confirm if it is an issue and when a patch might be released for your framework of choice . . .

I didn&apos;t find the sample attack scenario to be sufficiently detailed to get my head around the actual level of concern this should evoke. Perhaps someone who&apos;s played with JS a little more than me might like to comment?
				
				</description>
				
				<category>AJAX</category>
				
				<pubDate>Mon, 02 Apr 2007 16:34:00 -0400</pubDate>
				<guid>http://www.pbell.com/index.cfm/2007/4/2/Javascript-Highjacking-Risk-for-AJAX-Apps</guid>
				
			</item>
			
		 	
			
			
			<item>
				<title>Generating Static XML with CF for Improving Performance</title>
				<link>http://www.pbell.com/index.cfm/2006/10/17/Generating-Static-XML-with-CF-for-Improving-Performance</link>
				<description>
				
				Andy Powell just posted a great article on &lt;a href=&quot;http://www.infoaccelerator.net/client/index.cfm/2006/10/17/Spry-and-ColdFusion--Improve-Performance-By-Cutting-Out-ColdFusion&quot;&gt;using a file cache to persist datasets as static XML files&lt;/a&gt; rather than having to get CF respond to your spry requests. Only tweak I&apos;d make would be an IsDirty or Publish mechanism which maps recordsets to changes in CF so whenever you updated the data through the app it would regenerate the appropriate XML files.
				
				</description>
				
				<category>AJAX</category>
				
				<pubDate>Tue, 17 Oct 2006 19:07:00 -0400</pubDate>
				<guid>http://www.pbell.com/index.cfm/2006/10/17/Generating-Static-XML-with-CF-for-Improving-Performance</guid>
				
			</item>
			
		 	
			</channel></rss>
	

