I have some javascript in a standard HTML page that uses the ubiquitous
"XMLHttpRequest" to send data to a remote ASP page.

If that page "answers back" by sending a string using a simple
Response.Write, which I then use in the original HTML page to
dynamically update stuff, is this "AJAX"?

Specifically, is there anything "wrong" with sending back info from
classic ASP pages using simple Response.Writes? (Is there usually
something more required in the "answer back"? Or something that
Response.Write might not be sending, like an appropriate header "AJAX"
header?)

I mean, what I have done works! -- so I wonder if I am missing
something? It seems so easy to do -- I _MUST_ be missing something?
Right?

Thanks,
Blue Apricot
PS: Sorry about an "off topic" post, but I figured there would be some
AJAX experts here...

Thus wrote blueapricot416@gmail.com,

[quoted text, click to view]

It's Asynchronous, it's JavaScript, And it uses XMLHTTPRequest -- yes, that's
pretty much it.

[quoted text, click to view]

Wrong? No. It's probably neither the ideal component type nor the ideal technology,
but if it works for you...

[quoted text, click to view]

There's really no such thing like an "AJAX protocol" -- what's being sent
back over the wire can be whatever works best for you, or whatever you need
to interoperate with: SOAP, POX, JSON, or raw text.

[quoted text, click to view]

Don't forget that your current scenario was kind of thankful. It seems you
didn't have to deal with cross-browser compatibility issues, or more advanced
integration scenarios like pulling data from a Web service. You also didn't
need to integrate your approach with ASP.NET's page model. Things can get
bit more interesting if you're facing such issues. That's why you rather
want to use a good ASP.NET AJAX framework instead of making up your own.

Cheers,
--
Joerg Jooss
news-reply@joergjooss.d