Erik de Castro Lopo wrote:
Matthew Palmer wrote:
Why am I thinking that some partially-clued management type has already
decreed to some poor sod that they need to send all of the JS and such for a
site via AJAX,
Actually no, its not that bad at all.
The situation is that we are moving a web site from a microsoft
system to a Linux/Drupal system. However, part of the existing
system includes a whole bunch of C# .NOT stuff that talks to a
database backend.
The reason we are thinking about AJAX is because we think that
with AJAX we can simply talk XML to the existing code/database
and use AJAX to specify how the XML data is displayed.
AJAX is just a way to use existing standards and tools, like javascript
and XML
One reason we use AJAX is to create responsive, faster, and more
user-friendly Web applications.
Javascript by itself had no way of sending information between the Web
browser and the
Web server. AJAX remedy the situation by using XMLHttpRequest, the
technique
used at the heart of this technology.
With the classic HTML, if you wanted to get any information from a
database on
the server, or send user information to a server-side script, you had to
make
an HTML form to GET or POST. The user would then have to click "Submit",
wait for the server to respond, then a new page would load with the
results. Many
of us realised how much time we had to wait for the HTML page to load
each time.
AJAX remedies this bottleneck by sending forwards and back ONLY NEEDED
data to and from the server.
If you are using databases, you still have to provide the interface and
the scripting
to achieve the intended results.
O Plameras
_______________________________________________
coders mailing list
[email protected]
http://lists.slug.org.au/listinfo/coders
