I was one of the ones who jumped on the AJAX bandwagon pretty quickly. I've built several private apps using AJAX, and really like it. I like the fact that the web becomes more "rich," and more closely resembles forms in functionality. The gains are enormous. That having been said, I found myself asking the question: Is it worth it? I've found (so far) that doing things with AJAX takes at least three times longer, there's much more room for error, and cross-browser issues are brought to the forefront. ......
Just ran across this travel site that I'd not heard of before.
www.kayak.com
It's got some sweet AJAX action going on.
Recently, I've run across several posts over at the AJAX.NET Google Group asking about how you can bind a DataGrid, or a Repeater using AJAX. The answer is, you can't.DataGrids and Repeaters are Server Side controls. Their life begins and ends on the server, when the page is rendered to the client. The client is rendered to HTML, and sent to the client. That's it. Finito. The End. That's all she wrote. From there on out, it's all the client. Any AJAX transactions that take place must be rendered ......
Well, I deployed my first AJAX.NET project today. It's a private (local) project for a client. I like the benefits of AJAX technology, but there are a few quirks that should be dealt with.For instance, session time-outs. If you use any kind of session based authentication system, a time-out may occur if the page is not refreshed within the session time-out limit. Back-Button issues (as some have pointed out) are less of a big deal in this project ......
Over on the AjaxPro Google Group, a user asked a question about databinding a repeater using Ajax. The response has always been "A repeater (or any other server control) is rendered on the server, and then passed back to the client as HTML." One of the purposes of Ajax is to reduce the amount of bytes being sent back and forth between server and client on non-initial load functions. In this post, the usual answers were given. Loop through the dataset with JavaScript, then display the results. This ......
Which is better? This: <AjaxMethod()> _Public Function GetString() as String return "The String"End Function<Script> function getTheStringCallback(res) { document.write("<table&g... + res.value + "</td></tr><... }</Script>Or This: <AjaxMethod()> _Public Function GetString() as String Return " The String"End Function<SCRIPT> function getTheStringCallback(res) { document.write(res.value); }</SCRIPT>When writing AJAX ......
This...<AjaxPro.AjaxMeth... _Public Function GetTheDate(ByVal TheDate as DateTime) as String Return TheDate.ToShortDateStringEnd FunctionDoes not work.But, this...<AjaxPro.AjaxMeth... _Public Function GetTheDate(ByVal TheDate as String) as String Return cDate(TheDate).toShortDateS... FunctionDoes. Apparently, any type conversions involving dates need to be done inside the function, rather than passed through the function ......
The Psychology of AJAX If you’ve been poking around the .NET blogs long enough, you’ve seen the word AJAX, perhaps even visited Michael Schwarz’s website, maybe even downloaded his AJAX.Net assembly and poked around in it. I know I have. I see the value in AJAX, and that’s not what this post is about. I want to ask the audience some questions regarding the psychology of AJAX. The thing that got me interested in AJAX was a post about the way Sam Goody was incorporating it into ......