| There are some fast food outlets that
| |
| | you back a result (an example is
|
| start cooking food only after you walk up
| |
| | attempting to fetch images from certain
|
| to the counter and order it. Make no
| |
| | online photo sharing sites).But suppose
|
| mistake, these are the inefficient
| |
| | your desktop had a program in it which
|
| outlets. You end up waiting half an hour
| |
| | anticipated what your next request could
|
| for your meal to appear and vow never to
| |
| | be, got that information ahead of time
|
| go the restaurant again because of the
| |
| | from the server, and kept it ready for
|
| time it made you waste.Switch to a
| |
| | your browser. When you did make the
|
| well-organized fast-food outlet. Popular
| |
| | request, the information you wanted would
|
| menu items are already waiting for you in
| |
| | be readily available in your desktop. You
|
| the brightly lit 'keep warm' showcase.
| |
| | would not have to wait for it to be
|
| You walk up to the counter, order a
| |
| | fetched from the server; the program
|
| burger with fries, the salesperson goes
| |
| | gives it to your browser and it is
|
| to the showcase, takes out a warm,
| |
| | displayed immediately.Now think of the
|
| packaged burger, takes out fries and
| |
| | 'keep warm' showcase strategy in the fast
|
| gives them all to you in a jiffy.AJAX is
| |
| | food restaurant. You see the similarity
|
| a strategy for giving you web pages in a
| |
| | in concepts?So here's the thing: the
|
| jiffy. I can't but help thinking that
| |
| | program in your desktop that anticipates
|
| Jesse James Garrett, credited with being
| |
| | your next move and 'pre-fetches' data
|
| the brain behind AJAX, spent a lot of
| |
| | from the server is called an 'AJAX
|
| time at the best fast food outlets. Why?
| |
| | Engine'. It is written in the JavaScript
|
| Because the AJAX strategy is uncannily
| |
| | programming language.When it pre-fetches
|
| similar to that used in a quality fast
| |
| | data from the server, it uses a
|
| food establishment.Let's think for a
| |
| | programming language called XML.The
|
| moment about how your browser (Internet
| |
| | pre-fetching does not occur as a result
|
| Explorer, Firefox, whatever) fetches a
| |
| | of your request for a page. It happens at
|
| web page for you. You type the URL for
| |
| | other times, perhaps while you are
|
| the page into your browser. Your browser
| |
| | sitting back and viewing the last page
|
| sends a request to a computer on the
| |
| | that was sent. The pre-fetching is thus
|
| internet (the 'server' at that URL) to
| |
| | not synchronized with your requests for
|
| send that page back. The server pulls the
| |
| | pages. This is known technically as
|
| page out from its store of pages and
| |
| | asynchronous pre-fetching.Hence the name
|
| sends it to your browser, which displays
| |
| | Asynchronous JavaScript And XML, AJAX
|
| the page on your screen.Usually you do
| |
| | for short. And guess what, Google Groups,
|
| not have to wait more than 15 seconds for
| |
| | Google Suggest, and Google Maps are all
|
| the page to reach your browser and be
| |
| | implemented with AJAX.It is likely that
|
| displayed on your screen.But sometimes it
| |
| | AJAX is going to show up more frequently
|
| can take a whole half minute (which is
| |
| | in the design of interactive websites in
|
| the same as 'forever' in Internet terms)
| |
| | the coming years. Now you do not have to
|
| to see your page. Usually this occurs in
| |
| | wonder what it is!Lucky Balaraman is a
|
| a situation where you have entered some
| |
| | graduate engineer and one of the founders
|
| data in a web page, sent it down the
| |
| | of The Magnum Group, a leading web design
|
| Internet to a server, and are expecting
| |
| | and CAD service provider based at
|
| the server to process your data and send
| |
| | Chennai, India.
|
