WANT some detail on AJAX

[Bugsy]

hi fellows pro,,,,,
i want some details regarding AJAX. can anyone help me in that ....


reply me with some good articles as well as tutorials in (.net)

 

[Dag Sunde]

hi fellows pro,,,,,
i want some details regarding AJAX. can anyone help me in that ....


reply me with some good articles as well as tutorials in (.net)

Google!

 

[bwucke]

Bugsy napisal(a):

hi fellows pro,,,,,
i want some details regarding AJAX. can anyone help me in that ....


reply me with some good articles as well as tutorials in (.net)

http://www.usabilityviews.com/ajaxsucks.html
(disregard the 'spoof' part, all points still hold.)

 

[Thomas 'PointedEars' Lahn]

Its a relatively new technology

It is not.

(well a new name anyhow) most of the commnets int he article Bwucke refers
to are 'sort of right but wrong' AJAX pages are active and should be
hidden form search engines like any other cgi stuff.

Nonsense. First, it is entirely possible to create (X)HTML documents
that work both with and without "AJAX" support. Second, there is no
reason why resources generated by CGI applications should be hidden
from search engines.


PointedEars

 

[Thomas 'PointedEars' Lahn]

I agree its perfectly possible to create acceptable HTML docs from AJAX

"create ... from AJAX"? You have not even understood what I was talking
about; let alone quoted what you are replying to, as strongly recommended
by the newsgroup's FAQ:

<URL:http://jibbering.com/faq/faq_notes/pots1.html#ps1Post>

[...] However if the content will change regularly then the search
engines will waste the searchers time and your servers time cpu by
trying to take you to pages that 'no longer exist'.
The original idea behind robots.txt was to stop your server being
hammered by search engines. Now you should use it on your DYNAMIC
content pages so search engines dont point to expired data.

Rubbish. Have you even understood what /you/ are talking about? An
important part of the idea behind CGI and similar applications is that
similar content can be generated through a template, instead of files
with similar structure but different data. It is complete nonsense to
hide that generated content from search engines because, after all, you
want to be found due to the content you provide.

Learn about caching techniques, redirection and search engine optimization,
in general get informed, before you utter further nonsense here. Nobody is
helped with your half-knowledge but it does harm to those that actually
believe you.


PointedEars

 

[VK]

Learn about caching techniques, redirection and search engine optimization,
in general get informed, before you utter further nonsense here. Nobody is
helped with your half-knowledge but it does harm to those that actually
believe you.

Off the prozac again? I told you it's too early yet!

One brainless, other is humanless (by someone's recent definition).
Reminds me something from Futurama. Poor clj...



Besides all possible materials one can find in the Internet it is a
must I guess to read the original article where the term "AJAX" has
been introduced (and all the rush started):

<http://www.adaptivepath.com/publications/essays/archives/000385.php>

There are also interesting (from *my personal biased point of view*)
discussions in this group:

<http://groups.google.com/group/comp..._frm/thread/f6ce0a5e95d8bf30/95c4d63e4c82f068>

and here:

<http://groups.google.com/group/comp..._frm/thread/77a9c7235d624b61/292d292553d024f7>

Also while reading current articles one has to remember that
XMLHttpRequest / AJAX is not just a technologies anymore. It's a
business too: a lot of money has been invested (and not amortizated
yet) to different "AJAX Solutions" - and a lot of people are getting
their current payroll check grace to AJAX. So it's a golem structure
now (in sociological sense). It is able and it will fight for its
existence using its underlaying units (people). So the ping-pong game
"sucks - doesn't suck" will get more and more intensive and arguments
will be more and more senseless (but full of sense to whoever write
whem).

 

[Michael Winter]

On 04/01/2006 16:43, VK wrote:

[snip]

So the ping-pong game "sucks - doesn't suck" will get more and more
intensive and arguments will be more and more senseless (but full of
sense to whoever write whem).

Then perhaps it should be ended here, in this thread. AJAX, in itself,
doesn't 'suck' (though the abbreviated name does :-D). However, it's
very easy to apply it badly. GMail, when it was first released, is an
obvious example of such an application.

If AJAX is used in the way that all scripts should be on the Web,
there's no problem with it.

Mike

 

[bwucke]

I agree its perfectly possible to create acceptable HTML docs from AJAX
[...] However if the content will change regularly then the search
engines will waste the searchers time and your servers time cpu by
trying to take you to pages that 'no longer exist'.
The original idea behind robots.txt was to stop your server being
hammered by search engines. Now you should use it on your DYNAMIC
content pages so search engines dont point to expired data.

Rubbish. Have you even understood what /you/ are talking about? An
important part of the idea behind CGI and similar applications is that
similar content can be generated through a template,

Yes. Many terabytes of similar content. And the robots won't care if
it's similar as long as it differs even slightly. If you write Towers
of Hanoi in CGI, the user will play by following one line of links,
towards the victory. Bandwidth used: up to 1MB. The robot will try to
download ALL possible combinations. Bandwidth used: several gigabytes,
until you cut it off.

It is complete nonsense to
hide that generated content from search engines because, after all, you
want to be found due to the content you provide.

It may be undesired to hide IMPORTED content from search engines - if a
page is generated with a template and content pulled from database,
then yes. If the content is GENERATED then storing it in search engine
is usually complete nonsense. Search results, temporary statistics,
generated navigational shortcuts, personal user settings,
cross-references in source code - all the cases where the number of
pages generated by server from 'n' of fixed content isn't O(n) but
O(exp(n)) or similar.
I bet Mozilla Foundation would gladly open LXR for caching by Google if
you're ready to pay their bandwidth bills.

If the content is generated/downloaded by AJAX, most likely the search
engines will never see it. If you include it 'redundantly' from server
in the same pages, you miss the whole point of using AJAX which is
cutting on amount of data transmitted. If you allow accessing it
alternatively to AJAX pages, then including the AJAX pages in search
engines misses the point as they don't contain the content, just
scripts.

Learn about caching techniques, redirection and search engine optimization,
in general get informed, before you utter further nonsense here.

Learn about basic server costs management, creating
searchengine-friendly content (as opposed to link farms and tons of
crap called "search engines optimization" which buys you a week with
pagerank 4 and a place above competition and then a manual bittchslap
from a Google operator, sending your company's page into oblivion) and
in general get a clue.

Nobody is
helped with your half-knowledge but it does harm to those that actually
believe you.

ditto.