Slashdot Mirror
Microsoft to Release AJAX Framework
An anonymous reader writes "News.com is announcing that Microsoft has announced plans to release a JavaScript client framework library for use with ASP.NET 2.0 that makes AJAX style browser clients easier to code. Developers who attend Microsoft's PDC conference in September have been promised an early release of the code."
Now maybe I'm just entirely on crack here, but didn't Google recently announce or imply that they're going to be releasing their own internal AJAX framework?
here is what it looks like
I'll take that bet. Scott Guthrie (project load on the Web Platform and Tools Team at Microsoft) has stated that Atlas client script will work on all modern browsers, and will not be restricted to any web server.
You can read more on his weblog.P
Lets remember that Microsoft created the XMLHTTP objects that AJAX is built on.
Ok, resume bashing.
Top 10 Reasons To Procrastinate
10.
You've not used ASP.NET have you? All of the generated HTML and Javascript is guaranteed to work in all major modern browsers. True, some of the cooler DHTML stuff only works in IE, but other browsers get less cool but still functional equivalents.
Or, you know, you could just mindlessly bash MS, it's your choice.
It's official. Most of you are morons.
While I agree that Microsoft's way leaves much to be desired (primarily because AJAX on IE requires that you leave your browser open to ActiveX insercurities), I'm afraid there isn't really a "correct" way to do it. Your way (testing for the native XMLHttpRequest object, and then falling back to the ActiveX object if necessary) is certainly the best way, however.
IIRC, Mozilla's XMLHttpRequest object was created to mimic the functionality of Microsoft's ActiveX version, and then Safari and Opera (to a certain extent) followed suit. However, the XMLHttpRequest has never been part of ECMAScript (the standard that Javascript is based on) nor the W3C DOM. It has always been an "extension" that Microsoft has foisted upon the world, much like the <marquee> tags and layers we love to hate.
As such, it is inconsistently supported -- particularly in Opera and Safari 1.3/2.0. There are also minor differences (e.g. the number of arguments that the send method accepts) that arise due to the lack of a standard specification.
Fortunately, because of its immense utility in creating modern web-apps, it has become a de-facto standard and thus rather reliable. I would love to eventually see browsers support a standards-based version of AJAX (something like the W3C Level 3 DOM Load and Save specification), but until then, there is no truly "correct" way to do it.
You've never used the XmlHttpRequest object, have you? There is one version of it for IE, which is an ActiveX object. There is another for every other browser. Once you get that object, they are almost completely functionally the same. But if Microsoft makes their library only use the ActiveX version, then it simply won't work on anything except IE/Win. And that's not the fault of any other browser.
By the way, there is no standard yet. XmlHttpRequest is a non-standard technology at the moment.
Lack of eloquence does not denote lack of intelligence, though they often coincide.
there are a lot of them...
Sarissa - http://sarissa.sourceforge.net/doc/
Prototype - http://prototype.conio.net/
Dojo - http://dojotoolkit.org/
SAJAX - http://absinth.modernmethod.com/sajax/
DWR - http://www.getahead.ltd.uk/dwr/
JSON-RPC-Java - http://oss.metaparadigm.com/jsonrpc/
While people are busy promoting ajax on rails and so on, there is already a great AJAX Library for .net called Ajax.net
http://weblogs.asp.net/mschwarz/
Works like a charm
Lets face it;
.NET and now this.
.NET platform produces when you use it to create a simple HTML-form? Let me tell you this my friends, its horrid, ugly and terrible. There was a time where I believed that .NET for the 'net perhaps was something MS had done right. Not so, Sir Willian.
90% of the programmers in the MS area are morons. They are not interested in the higher aspects of computer science, nor do they give a shit about compability or efficient code. They care about one thing.
Does it do what I want?
This might sound fine and good to a lot of people, unfortunatly it isn't very so. We all remember the MESS frontpage created on the internet, zillions of so called webmasters broke the gates of pearls we had between THEM and US, the programmers. Now they're back, and they're punching with
Have anyone here LOOKED at what the Visual
ASP.NET (in .net 1.1) already doesn't work without javascript more or less.
ASP.NET can downgrade to both scriptless and cookieless operations, which was one of the major selling points of it. In fact out of the box it presumes too little out of most clients, though thankfully you can update the browsercaps quite easily.
One of the great things about "AJAX" is that the "X" is optional. No reason to do XML at all unless that's what you want. So, if XML is overkill for your application, take a look at JSON, http://www.json.org/
I think it's better than CSV even. And it's got bindings to tons of languages, not just Javascript. So producing the server-side is also very easy.
And your knowledge is pretty far off-base.
Do you realize the XMLHttpRequest Object (the core javascript object in which AJAX would not exist without) is not a W3C standard? It was first implemented in IE5 as an ActiveX Object (new ActiveXObject("Microsoft.XMLHTTP")) and latered implemented by Mozilla, Firefox, Safari, etc.
Of course, you won't find anyone giving MS credit for innovation here, but you'll get modded 5 if you're the first to mentions "standards!"
if Microsoft hadn't invented Ajax.
Have you ever been to a turkish prison?
Mr. "Senior Programmer" Your comment is not standards compliant. It's called ECMAScript.