extjs vs ajax

[lyealain]

hi.. i wonder which is the best to use for these 2 .. extjs or ajax?
i know nothing for extjs ..but i like those interface..
do i need to write more js code for extjs compare to ajax ? pls comapre these 2
i am doing .NET project thanks

[Animal]

Your operator is wrong.

extjs >= ajax

[kieren.johnson]

Well ... you need to consider a number of factors. What licensing is available for this AJAX framework? Is it compatible with the project you are working on? Does it come with a bunch of useful APIs that make coding so much easier??

... OK. I'll stop now. Your question doesn't make sense. AJAX is a term that describes a system for transferring data from the browser to the server and back again without a page refresh. ExtJS is a complete framework of user interfaces that make coding applications that use AJAX much easier.

[elishnevsky]

Your operator is wrong.

extjs >= ajax

LOL :D

[FlaminPhoenix]

huh? the relationship is more like extjs uses ajax.. I can only guess that the OP is talking about comparing raw javascript XMLhttp request against the Ajax class in ext..

@ OP: If youre looking at doing a .net project that is for a client, youd probably be better off using extjs.. if youre doing a student project, just to pass your exams, then too, extjs wins, hands down!

[steffenk]

Your operator is wrong.

extjs >= ajax

good catch :)

[alien3d]

Your operator is wrong.

extjs >= ajax
Become

extjs >= ajax(xml) => ajaj(json) => ajas(soap):-?

[Mike Robinson]

The term, "AJAX," literally refers to the way that the client and the host work with one another: what they say to each other, when they say it, and what the messages contain.

ExtJS is a JavaScript framework that simplifies the use of AJAX techniques, by doing essentially all of the client-side foundation coding for you.

In a standard HTML page, the server sends you ... an HTML page. You display what it sends you. No thought required. :) The client is little more than a half-duplex dumb terminal (without the "IBM 3270" label). It just draws pretty pictures. Duh. And what a waste of a perfectly good desktop computer, eh?

In an AJAX situation, there's an actual front-end program, written in JavaScript and using ExtJS, running on the client computer, and the user is interacting mostly with that program. Meanwhile, that JavaScript program is exchanging information, "program to program," with the host. The information exchange uses the same HTTP protocol that is used for other purposes, but the exchange consists ... not of HTML pages, but of requests and subsequent replies to those requests. ("The host is not talking directly to you... it is talking to another program.") The end-user does not observe those exchanges, and does not have to wait for them: they happen "asynchronously." (Hence the "A" in "AJAX.")

When the client and the host talk to another, there must be an agreement as to how the data being exchanged will be encoded. The only technical requirement is that it must be "in some HTTP-compatible way," and that all parties concerned must agree on what it shall be. XML is one way to do it; JSON is another. SOAP is an XML-based format that's really good for cordial communication between two computers that really don't know one another too well.

HTH ...