Foundations of Ajax briefly mentions an example in chapter 2 that uses remote scripting using iframes rather than the XMLHttpRequest object.
Remote scripting has a few advantages, namely that it can be used in any browser that supports iframes and it can connect to other domains. Other than that, from a developer standpoint, using the XMLHttpRequest object is the superior choice.
Ryan Asleson<br />Co-Author, <a href="http://www.amazon.com/Foundations-Ajax-Foundation-Ryan-Asleson/dp/1590595823/sr=1-1/qid=1158926537/ref=pd_bbs_1/002-7412154-2924860?ie=UTF8&s=books" target="_blank" rel="nofollow">Foundations of Ajax</a> and <a href="http://www.amazon.com/Pro-Ajax-Java-Frameworks/dp/1590596773/ref=sr_11_1/002-7412154-2924860?ie=UTF8" target="_blank" rel="nofollow">Pro Ajax and Java Frameworks</a><br /><a href="http://taconite.sf.net" target="_blank" rel="nofollow">Taconite</a> Lead Developer
Yeah I am a .NET developer here in a world surrounded by Java people.
Remote Scripting is another term for Ajax. You probably looked at the remotescripting library that was avaiable for .NET.
I highly resommend using Ajax in the .NEt framework. With Ajax In Action I have an example in vb.net and C#. I just got a new job where I will be integrating Ajax functionality into the next version of the application.
IMHO: Tha main goal for Ajax is to increase the user's experience. The whole application does not have to be Ajax. A single ajax component on the page can make a sour user turn into a sweet one.
Now with .NET on the 2.0 framework you can look into ATLAS. I just started to do that, but I am not a really big fan of the whole tag nature of it. Plus the documentation is still not great. The ASP.NET forums has a whole section devoted to atlas.
keep an eye out for scorpions and black widows. But the tiny ads are safe.