469,898 Members | 2,328 Online
Bytes | Developer Community
New Post

Home Posts Topics Members FAQ

Post your question to a community of 469,898 developers. It's quick & easy.

AJAX, XMLHttp, and webservice.htc. interesting find...

Jay
Getting into AJAX using the XMLHttp object and am really liking it.

We are in the process of upgrading our existing behavior calls
(webservice.htc) to the more 'supported', as they say, concept of
AJAX. One thing I noticed was that the .htc code practically does the
same thing AJAX does - with nice code that allows you to .value
reference the return XML nice and easily - and now I'm wondering why I
should even bother trying to reinvent the wheel.

The one thing I noticed so far that really looked like an issue is
that the .htc file uses the older 'Microsoft.XMLHttp' object. As far
as I know, there are newer versions (and I'm guesing faster as well)
such as 'MSXML2.XMLHttp.5.0'. I tried to hack the code to instantiate
the 5.0 object and it blew up. I am assuming this is due to the fact
that webservice.htx is not backwards compatible and/or hardcoded
specifically for the 'Microsoft.XMLHttp' object.

Has anyone come across this situation? Is there much to gain by moving
from 'Microsoft.XMLHttp' to 'MSXML2.XMLHttp' object? Should I just
keep the webservice.htc and continue using it, or is it worth to dive
in and upgrade to the newer AJAX stuff?

Thanks for your thoughts...

Oct 12 '07 #1
2 3162
Jay
On Oct 12, 3:37 pm, Jay <Jay.Pomp...@gmail.comwrote:
Getting into AJAX using the XMLHttp object and am really liking it.

We are in the process of upgrading our existing behavior calls
(webservice.htc) to the more 'supported', as they say, concept of
AJAX. One thing I noticed was that the .htc code practically does the
same thing AJAX does - with nice code that allows you to .value
reference the return XML nice and easily - and now I'm wondering why I
should even bother trying to reinvent the wheel.

The one thing I noticed so far that really looked like an issue is
that the .htc file uses the older 'Microsoft.XMLHttp' object. As far
as I know, there are newer versions (and I'm guesing faster as well)
such as 'MSXML2.XMLHttp.5.0'. I tried to hack the code to instantiate
the 5.0 object and it blew up. I am assuming this is due to the fact
that webservice.htx is not backwards compatible and/or hardcoded
specifically for the 'Microsoft.XMLHttp' object.

Has anyone come across this situation? Is there much to gain by moving
from 'Microsoft.XMLHttp' to 'MSXML2.XMLHttp' object? Should I just
keep the webservice.htc and continue using it, or is it worth to dive
in and upgrade to the newer AJAX stuff?

Thanks for your thoughts...
One bump.

Any thoughts at all?

Thank you...

Oct 15 '07 #2
Jay wrote:
Getting into AJAX using the XMLHttp object and am really liking it.

We are in the process of upgrading our existing behavior calls
(webservice.htc) to the more 'supported', as they say, concept of
AJAX. One thing I noticed was that the .htc code practically does the
same thing AJAX does - with nice code that allows you to .value
reference the return XML nice and easily - and now I'm wondering why I
should even bother trying to reinvent the wheel.

The one thing I noticed so far that really looked like an issue is
that the .htc file uses the older 'Microsoft.XMLHttp' object. As far
as I know, there are newer versions (and I'm guesing faster as well)
such as 'MSXML2.XMLHttp.5.0'. I tried to hack the code to instantiate
the 5.0 object and it blew up. I am assuming this is due to the fact
that webservice.htx is not backwards compatible and/or hardcoded
specifically for the 'Microsoft.XMLHttp' object.

Has anyone come across this situation? Is there much to gain by moving
from 'Microsoft.XMLHttp' to 'MSXML2.XMLHttp' object? Should I just
keep the webservice.htc and continue using it, or is it worth to dive
in and upgrade to the newer AJAX stuff?
I'm not an expert in this matter, but I surmise that MS Internet
Explorer should select the most recently installed version by default,
that is, if you don't specify anything else.

You might have a good reason to request for a specific version, but I
wouldn't do too much exotic or version-dependent stuff if you want
your scripts still working after some time.

It looks like this is more a topic for the Microsoft-specific
newsgroups (their own engineers are on it):
http://www.microsoft.com/communities...s/default.aspx

Hope this helps,

--
Bart

Oct 15 '07 #3

This discussion thread is closed

Replies have been disabled for this discussion.

Similar topics

4 posts views Thread by bobzimuta | last post: by
6 posts views Thread by Joel Byrd | last post: by
1 post views Thread by trpost | last post: by
17 posts views Thread by Arjen | last post: by
1 post views Thread by Nithu25 | last post: by
8 posts views Thread by Rory Becker | last post: by
By using this site, you agree to our Privacy Policy and Terms of Use.