prototype = new XMLHttpRequest()? why not?

Ok, all over the internet people are creating "wrapper" object over
XMLHttpRequest rather then prototyping it and I wonder why, are there
any drawbacks for this method? I couldn't find much info about it on
google..

Thanks for replies

On Mar 3, 3:50 pm, Piotr K <piotr.korzeniew...@gmail.comwrote:

Quote:

Ok, all over the internet people are creating "wrapper" object over
XMLHttpRequest rather then prototyping it and I wonder why, are there
any drawbacks for this method? I couldn't find much info about it on
google..
>
Thanks for replies

I don't think IE6 will allow you to protoype the xmlhttprequest
object. I don't know about IE7's native object.

Helbrax <linn.white@hotmail.comwrites:

Quote:

I don't think IE6 will allow you to protoype the xmlhttprequest
object. I don't know about IE7's native object.

It's worse than that: IE6 doesn't even /have/ an XMLHttpRequest object
as a property of the global object. IOW, there isn't anything to
"prototype". And looking at IE behaviour for other host objects, it's
doubtful you can usefully extend XMLHttpRequest's prototype on IE7,
though I haven't tried it.

--
Joost Diepenmaat | blog: http://joost.zeekat.nl/ | work: http://zeekat.nl/

prototype = new XMLHttpRequest()? why not?

re: prototype = new XMLHttpRequest()? why not?

re: prototype = new XMLHttpRequest()? why not?

Similar JavaScript / Ajax / DHTML bytes

/bytes/development

/bytes/it

/bytes/about