Comments on: ASP.NET AJAX History Part 1: Server-Side http://lostintangent.com/2008/02/06/aspnet-ajax-history-part-1-server-side/ Code is never finished, only abandoned... Fri, 29 Aug 2008 19:19:11 +0000 http://wordpress.org/?v=2.3.1 By: Mike http://lostintangent.com/2008/02/06/aspnet-ajax-history-part-1-server-side/#comment-510 Mike Wed, 02 Jul 2008 20:40:00 +0000 http://lostintangent.com/2008/02/06/aspnet-ajax-history-part-1-server-side/#comment-510 @John: Yeah, it's a lot of code, and brittle too, with the string keys for history points. It's major plumbing to get functionality the browser already has (it's not called a browser for nothing). Basically, using Ajax for full navigation is in many cases overkill. However, when you are creating a single window web application (think of the Outlook example you often see) than you really need to do this. @John:

Yeah, it’s a lot of code, and brittle too, with the string keys for history points. It’s major plumbing to get functionality the browser already has (it’s not called a browser for nothing). Basically, using Ajax for full navigation is in many cases overkill.

However, when you are creating a single window web application (think of the Outlook example you often see) than you really need to do this.

]]> By: John http://lostintangent.com/2008/02/06/aspnet-ajax-history-part-1-server-side/#comment-411 John Thu, 05 Jun 2008 00:35:49 +0000 http://lostintangent.com/2008/02/06/aspnet-ajax-history-part-1-server-side/#comment-411 This is a great feature/article on asp.net ajax, however I think it's still a pain in the arse to manually restore a state of a webpage, especially when the page is more than a trivial design with user controls embedded into it and other components you can not manually set. For me, using such a manual restore feature would make my job twice as hard and take twice as long, just to get the same result as a full postback would give me. I've come to the conclusions that I'll only use MS Ajax where I don't need to restore the page state and just for simple updates within the page. Is anyone else having the same thoughts? This is a great feature/article on asp.net ajax, however I think it’s still a pain in the arse to manually restore a state of a webpage, especially when the page is more than a trivial design with user controls embedded into it and other components you can not manually set. For me, using such a manual restore feature would make my job twice as hard and take twice as long, just to get the same result as a full postback would give me. I’ve come to the conclusions that I’ll only use MS Ajax where I don’t need to restore the page state and just for simple updates within the page. Is anyone else having the same thoughts?

]]> By: Robert http://lostintangent.com/2008/02/06/aspnet-ajax-history-part-1-server-side/#comment-375 Robert Tue, 20 May 2008 17:14:54 +0000 http://lostintangent.com/2008/02/06/aspnet-ajax-history-part-1-server-side/#comment-375 What if more than one item is selected? What if more than one item is selected?

]]> By: Trevor http://lostintangent.com/2008/02/06/aspnet-ajax-history-part-1-server-side/#comment-198 Trevor Mon, 10 Mar 2008 11:41:59 +0000 http://lostintangent.com/2008/02/06/aspnet-ajax-history-part-1-server-side/#comment-198 Thanks for the article, and thanks for not having the entire history of AJAX taking up the first 23 paragraphs of your article. It's very nice to read an author who gets to the point. Thank you. Thanks for the article, and thanks for not having the entire history of AJAX taking up the first 23 paragraphs of your article. It’s very nice to read an author who gets to the point. Thank you.

]]> By: Julie Lerman http://lostintangent.com/2008/02/06/aspnet-ajax-history-part-1-server-side/#comment-138 Julie Lerman Thu, 07 Feb 2008 03:37:43 +0000 http://lostintangent.com/2008/02/06/aspnet-ajax-history-part-1-server-side/#comment-138 I'm with Timothy - sweet and powerful feature. And thanks to the way you have explained it, it makes perfect sense and sounds really easy to use. I'm going to go figure out where I can sneak it into a demo! I’m with Timothy - sweet and powerful feature. And thanks to the way you have explained it, it makes perfect sense and sounds really easy to use. I’m going to go figure out where I can sneak it into a demo!

]]> By: Timothy Khouri http://lostintangent.com/2008/02/06/aspnet-ajax-history-part-1-server-side/#comment-137 Timothy Khouri Thu, 07 Feb 2008 03:06:29 +0000 http://lostintangent.com/2008/02/06/aspnet-ajax-history-part-1-server-side/#comment-137 This is a seriously beautiful feature. When I first heard of the name, I thought of it as being something semi-lame (like a sort of "caching" the requests so that if called again, it would just be a faster response). But this is really very powerful, and simply amazing. Also, very good article. It describes the technology and makes it fun... I hate lame articles :P This is a seriously beautiful feature. When I first heard of the name, I thought of it as being something semi-lame (like a sort of “caching” the requests so that if called again, it would just be a faster response).

But this is really very powerful, and simply amazing. Also, very good article. It describes the technology and makes it fun… I hate lame articles :P

]]>