Comments on: Using serialized JSON to move complex data to and from the browser http://elegantcode.com/2009/11/06/using-serialized-json-to-move-complex-data-to-and-from-the-browser/ Mon, 15 Mar 2010 17:35:57 -0500 http://wordpress.org/?v=2.8.6 hourly 1 By: Tjerk http://elegantcode.com/2009/11/06/using-serialized-json-to-move-complex-data-to-and-from-the-browser/comment-page-1/#comment-50810 Tjerk Mon, 30 Nov 2009 21:25:28 +0000 http://elegantcode.com/2009/11/06/using-serialized-json-to-move-complex-data-to-and-from-the-browser/#comment-50810 You could take this even further and place the whole view layer (UI logic and events etc.) on the client and have the server just pass data back and forth. Some have named this 'SOFEA' or 'SOUI', others 'client-server 2', for example see http://www.it-eye.nl/weblog/2008/09/24/what-is-client-server-20/ You could take this even further and place the whole view layer (UI logic and events etc.) on the client and have the server just pass data back and forth. Some have named this ‘SOFEA’ or ‘SOUI’, others ‘client-server 2′, for example see http://www.it-eye.nl/weblog/2008/09/24/what-is-client-server-20/

]]> By: Jarod Ferguson http://elegantcode.com/2009/11/06/using-serialized-json-to-move-complex-data-to-and-from-the-browser/comment-page-1/#comment-50670 Jarod Ferguson Wed, 25 Nov 2009 08:07:20 +0000 http://elegantcode.com/2009/11/06/using-serialized-json-to-move-complex-data-to-and-from-the-browser/#comment-50670 @chris I dont think Jason was calling $.ajax here. The main point, which may have been missed was: "I am sensitive about the number of calls being made (which I was here)" The idea is to load the page with the JSON you know you will need in a hidden field during the initial webrequest. In this case you do not want to use $.getJSON. In doing so, you can keep the client logic in javascript/json instead of duplicating logic on the client in js on the server in c#. A simple example might be adding/removing items from a list. Its sorta kinda but not really like viewstate.... its a hidden payload, only for client data storage. On the server your only responsibility is change tracking what happened on the client. @chris

I dont think Jason was calling $.ajax here. The main point, which may have been missed was:

“I am sensitive about the number of calls being made (which I was here)”

The idea is to load the page with the JSON you know you will need in a hidden field during the initial webrequest. In this case you do not want to use $.getJSON.

In doing so, you can keep the client logic in javascript/json instead of duplicating logic on the client in js on the server in c#. A simple example might be adding/removing items from a list.

Its sorta kinda but not really like viewstate…. its a hidden payload, only for client data storage. On the server your only responsibility is change tracking what happened on the client.

]]> By: Jason Grundy http://elegantcode.com/2009/11/06/using-serialized-json-to-move-complex-data-to-and-from-the-browser/comment-page-1/#comment-50131 Jason Grundy Sat, 07 Nov 2009 00:46:01 +0000 http://elegantcode.com/2009/11/06/using-serialized-json-to-move-complex-data-to-and-from-the-browser/#comment-50131 <a href="#comment-50130" rel="nofollow">@Chris Brandsma</a> I definitely agree Chris although here I was referring to AJAX as a technique rather than as a JQuery method. I'll be more clear next time ;) @Chris Brandsma
I definitely agree Chris although here I was referring to AJAX as a technique rather than as a JQuery method. I’ll be more clear next time ;)

]]> By: Chris Brandsma http://elegantcode.com/2009/11/06/using-serialized-json-to-move-complex-data-to-and-from-the-browser/comment-page-1/#comment-50130 Chris Brandsma Fri, 06 Nov 2009 23:42:05 +0000 http://elegantcode.com/2009/11/06/using-serialized-json-to-move-complex-data-to-and-from-the-browser/#comment-50130 You need to move to using $.getJSON or $.post(url, data, success, "json") instead of calling $.ajax. Then you can get rid of most of the toJSON stuff. You need to move to using $.getJSON or $.post(url, data, success, “json”) instead of calling $.ajax. Then you can get rid of most of the toJSON stuff.

]]>