I have noted so much information on the internet about AJAX.
1. Does anybody have an experience with AJAX.
2. What is the advantages and do I need it?
Here is an AJAX offer I got in my email.
Do you think it is worth USD 50?
I have noted so much information on the internet about AJAX.
1. Does anybody have an experience with AJAX.
2. What is the advantages and do I need it?
Here is an AJAX offer I got in my email.
Do you think it is worth USD 50?
Mini Network:: Financial information at your fingertips
Learn object oriented programming where it started
Conversations creates communities and conversions create profit.
Hell no. This is just a marketing ploy.
Certainly not worth $50. Look on Amazon if you want an AJax book or there are some pretty good tutorials out there.
HTH
But what is it? Do I need it?
Mini Network:: Financial information at your fingertips
Learn object oriented programming where it started
Conversations creates communities and conversions create profit.
the definition of AJAX is Asynchronous JavaScript and XML and if you are heavy into web development, it is something you should probably learn or at least be aware of. if i'm not mistaken, the Google personalized homepage is done with AJAX. it gives you the ability to do things like drag and drop web modules when you are in the process of personalizing.
Mozilla has a good starter tutorial and i'm sure Google or Yahoo will reveal more.
Former WebProWorld Admin
IntentionalFoul.com
Yes, now I see it. I also found this great article by Jesse James Garrett:
Ajax: A New Approach to Web Applications
that according to your Wiki page was the first to use the term in public.
"Google Suggest and Google Maps are two examples of a new approach to web applications that we at Adaptive Path have been calling Ajax. The name is shorthand for Asynchronous JavaScript + XML, and it represents a fundamental shift in what’s possible on the Web".
Definitely something to take a closer look at.
Mini Network:: Financial information at your fingertips
Learn object oriented programming where it started
Conversations creates communities and conversions create profit.
I do all my coding server side. The only benefits ajax has is to instantly update the browser. But what happens if the user has turned off javascript? ajax becomes redundant.
I would rather have the page refresh and be 100% sure of data entered rather than use ajax and depend on only 85-90% (current estimates of javascript enabled users) of data entered. 10-15% may not be a lot in some peoples eyes but if you are dealing in large monetary value products then for the sake of a second or two to refresh the page and do calculations server side then that can translate to a lot of lost income. You are selling products worth $1000 then you are losing $100-150 for each potential sale?
For me ajax is a gimmick and a marketing "buzz word" if you ask the guys who work in the big money sector of the net ajax is a "No-No" it may be cool but it is not infallible and when it comes down to it you want your script/product to work out of the box on all possible server configurations and the only possible way to do that is server side programming. Client side programming has never and will never be a valid option for ecommerce.
Until the day that browsers are released that you cannot turn off javascript then ajax remains a toy for those who like to push the boundaries. Heck, I like cool stuff and have played with ajax and made it do some really, really neat stuff I might use on a personal page or show others how to do but for anything someone is paying me to programme then ajax does not even enter my thought process.
There is no possible situation that ajax can be benificial over server side programming. If your development firm are pushing the ajax boat then you are with the wrong firm.
"I have not failed. I have found 10,000 ways that don't work" - Thomas Edison.
"The secret to creativity is knowing how to hide your sources" - Albert Einstein.
Music in an economists ears and you love Linux too. I am still thinking of Linux, but I have not had the time to try it, especially with hot summer, fishing and outdoor life in Norway and Windows Vista around the corner.Originally Posted by Easywebdev
Mini Network:: Financial information at your fingertips
Learn object oriented programming where it started
Conversations creates communities and conversions create profit.
One of the issues that we should keep in mind here is simplicity served up!
I just converted www.huntandhunt.com to Google Maps from MapQuest.
Neither serves up validatable code, and you know what? - I don't give a rat's ass whether they do or not!
By nature there is some conflict between progressive inneractivity and the press for AJAX technology implementation, and those that are more more challenged in surfing. That's OK, but it does not need to penalize my site if I choose not to clean up the MapQuest or GooglrMaps sloppy code!
I also chose to map convert in quest of better localized SERP, and it is paying off immediately!
I am sorry, but I have to offer up the suggestion that "usability" for the non-disabled, is a much greater market and will always continue to be.
That is precisely why Google is forging ahead in AJAX developments.
The new position here:
Anyone that wants to surf with javascripts turned off... go for it! - sorry you lost out!
We are definitely seeing javascripting used appropiately making a rebound - IMO.
:)
Ken
Bottom line is; you lose control when you rely on client side scripting. AJAX is a nice tool to make pages more "user friendly" but should never be relied upon for a public web application to function properly, even efficiently.
What if you want dynamic reaction from the page (browser) when you move the mouse pointer across objects on the page?
In a nutshell, that is the difference between a Java applet and a Java servlet.Originally Posted by Vectorman211
Mini Network:: Financial information at your fingertips
Learn object oriented programming where it started
Conversations creates communities and conversions create profit.