<?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"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: JavaScript Persistent Object Notation (JSPON)</title>
	<atom:link href="http://ajaxian.com/archives/javascript-persistent-object-notation-jspon/feed" rel="self" type="application/rss+xml" />
	<link>http://ajaxian.com/archives/javascript-persistent-object-notation-jspon</link>
	<description>Cleaning up the web with Ajax</description>
	<lastBuildDate>Thu, 17 May 2012 07:43:39 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.2</generator>
	<item>
		<title>By: portrait artist</title>
		<link>http://ajaxian.com/archives/javascript-persistent-object-notation-jspon/comment-page-1#comment-258404</link>
		<dc:creator>portrait artist</dc:creator>
		<pubDate>Wed, 07 Nov 2007 06:06:38 +0000</pubDate>
		<guid isPermaLink="false">http://ajaxian.com/archives/javascript-persistent-object-notation-jspon#comment-258404</guid>
		<description>Forgive me for my non-techie skills but can anyone please tell me the difference between JSPON and JSON?</description>
		<content:encoded><![CDATA[<p>Forgive me for my non-techie skills but can anyone please tell me the difference between JSPON and JSON?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kirankumar</title>
		<link>http://ajaxian.com/archives/javascript-persistent-object-notation-jspon/comment-page-1#comment-134891</link>
		<dc:creator>Kirankumar</dc:creator>
		<pubDate>Wed, 18 Oct 2006 10:05:28 +0000</pubDate>
		<guid isPermaLink="false">http://ajaxian.com/archives/javascript-persistent-object-notation-jspon#comment-134891</guid>
		<description>Can we prepare dynamic graph at the client side which will show the speed of the charactor entered by the user.....</description>
		<content:encoded><![CDATA[<p>Can we prepare dynamic graph at the client side which will show the speed of the charactor entered by the user&#8230;..</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jason Haley</title>
		<link>http://ajaxian.com/archives/javascript-persistent-object-notation-jspon/comment-page-1#comment-79128</link>
		<dc:creator>Jason Haley</dc:creator>
		<pubDate>Fri, 01 Sep 2006 02:42:27 +0000</pubDate>
		<guid isPermaLink="false">http://ajaxian.com/archives/javascript-persistent-object-notation-jspon#comment-79128</guid>
		<description>&lt;strong&gt;Interesting Finds: August 31, 2006&lt;/strong&gt;

</description>
		<content:encoded><![CDATA[<p><strong>Interesting Finds: August 31, 2006</strong></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kris Zyp</title>
		<link>http://ajaxian.com/archives/javascript-persistent-object-notation-jspon/comment-page-1#comment-79099</link>
		<dc:creator>Kris Zyp</dc:creator>
		<pubDate>Fri, 01 Sep 2006 00:07:10 +0000</pubDate>
		<guid isPermaLink="false">http://ajaxian.com/archives/javascript-persistent-object-notation-jspon#comment-79099</guid>
		<description>Terry,
I took a look at your blog, very interesting to see you wresting with some of the same things I have.  The persistence issue is definitely not trivial. Anyway, I certainly do have an implementation behind this RFC.  (I was hoping that the RFC didn&#039;t look too implementation driven, so I am glad it you didn&#039;t notice). In my approach the server has the master object graph.  The client/browser then makes request for different objects from the server.  As they are delivered from the server they include identification per the spec.  Objects can be referenced that have been downloaded yet, and when the client encounters these objects, it can request them from the server.My approach is a little different because I am not attempting adhoc serialization of any JavaScript object, but rather all persistable objects are instances of certain constructor. When the server delivers object graph information from the server, the client creates JavaScript objects that are instances of the PersistentObject. It actually creates objects that are like Java beans, with getters and setters.  That way code can access fields through getters and the getters automatically handle retrieving data from the server when additional object graph data is necessary.  If a user wishes to add an peristent object to the persisted object graph they must instantiate from the PersistentObject constructor.  It then gives itself a temporary client side id, and once it is persisted to the server, the server gives it a permanent unique id for the master object graph.  This deals with id collision problem. This is why the JSPON spec provides an id field and a clientid field.  Newly created objects from a client should not attempt to assign their own id in the context of the master database, they can only assign themselves a temporary id within their own context until the server assigns a permanent one.
Anyway, my project is still under development, but just to see a little results, you can catch a glimpse of it in action when you visit www.authenteo.com.  You will notice there is basically no HTML for the page, rather JavaScript requests a root object from the object graph, and then builds the web page on the client side using object graph and requests are made from the server as needed for additional parts of the graph.  Even a lot of the code is delivered in the object graph.  Therefore the entire page rendering process takes place completely on the browser.  I think this is really an evolutionary approach, as you end providing a means for a true client centric model-view-controller programming model.  The logic processing of the application and displaying the web page and interacting with user is all centered on the browser, no awkward remote links in the MVC as occurs in almost all web applications, and the remote connection is just used for providing object graph information for the framework.  The server can then could do very effective look ahead caching to accelerate the process.
This is also really cool because it really lessens the load on the server, the server is never really doing any complicated page rendering, just delivering JSON/JSPON objects.  The browser does all the work.  And it is surprisely fast. A lot of the effective parsing is done by innerHTML calls which are extremely fast.</description>
		<content:encoded><![CDATA[<p>Terry,<br />
I took a look at your blog, very interesting to see you wresting with some of the same things I have.  The persistence issue is definitely not trivial. Anyway, I certainly do have an implementation behind this RFC.  (I was hoping that the RFC didn&#8217;t look too implementation driven, so I am glad it you didn&#8217;t notice). In my approach the server has the master object graph.  The client/browser then makes request for different objects from the server.  As they are delivered from the server they include identification per the spec.  Objects can be referenced that have been downloaded yet, and when the client encounters these objects, it can request them from the server.My approach is a little different because I am not attempting adhoc serialization of any JavaScript object, but rather all persistable objects are instances of certain constructor. When the server delivers object graph information from the server, the client creates JavaScript objects that are instances of the PersistentObject. It actually creates objects that are like Java beans, with getters and setters.  That way code can access fields through getters and the getters automatically handle retrieving data from the server when additional object graph data is necessary.  If a user wishes to add an peristent object to the persisted object graph they must instantiate from the PersistentObject constructor.  It then gives itself a temporary client side id, and once it is persisted to the server, the server gives it a permanent unique id for the master object graph.  This deals with id collision problem. This is why the JSPON spec provides an id field and a clientid field.  Newly created objects from a client should not attempt to assign their own id in the context of the master database, they can only assign themselves a temporary id within their own context until the server assigns a permanent one.<br />
Anyway, my project is still under development, but just to see a little results, you can catch a glimpse of it in action when you visit <a href="http://www.authenteo.com" rel="nofollow">http://www.authenteo.com</a>.  You will notice there is basically no HTML for the page, rather JavaScript requests a root object from the object graph, and then builds the web page on the client side using object graph and requests are made from the server as needed for additional parts of the graph.  Even a lot of the code is delivered in the object graph.  Therefore the entire page rendering process takes place completely on the browser.  I think this is really an evolutionary approach, as you end providing a means for a true client centric model-view-controller programming model.  The logic processing of the application and displaying the web page and interacting with user is all centered on the browser, no awkward remote links in the MVC as occurs in almost all web applications, and the remote connection is just used for providing object graph information for the framework.  The server can then could do very effective look ahead caching to accelerate the process.<br />
This is also really cool because it really lessens the load on the server, the server is never really doing any complicated page rendering, just delivering JSON/JSPON objects.  The browser does all the work.  And it is surprisely fast. A lot of the effective parsing is done by innerHTML calls which are extremely fast.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Terry Laurenzo</title>
		<link>http://ajaxian.com/archives/javascript-persistent-object-notation-jspon/comment-page-1#comment-78933</link>
		<dc:creator>Terry Laurenzo</dc:creator>
		<pubDate>Thu, 31 Aug 2006 15:21:30 +0000</pubDate>
		<guid isPermaLink="false">http://ajaxian.com/archives/javascript-persistent-object-notation-jspon#comment-78933</guid>
		<description>My apologies.  It looks like some of the formatting got stripped off of my previous comment.</description>
		<content:encoded><![CDATA[<p>My apologies.  It looks like some of the formatting got stripped off of my previous comment.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

