Search

You searched for the word(s): userid:753816

Matching Posts

  • Re: Difference between MSXML2.XmlHttp and Microsoft.XmlHttp ProgIDs

    Your right - I don't think using the deprecated namespace is the right way to go - also the code from Dojo above doesn't test for the lastest version (MSXML2.XMLHTTP.6.0). I use the following code (as per M$ recommendation): var tr = !!window.clientInformation, progids = [ 'MSXML2.XMLHTTP.6.0' , 'MSXML2.XMLHTTP.3.0' , 'Microsoft.XMLHTTP' ], sProgid = null ; // Wrapper for IE's ActiveObject if (tr && !window.XMLHttpRequest) { // Returns null if the ActiveX
    Posted to Client Side Web Development (Forum) by Wukfit on 1/29/2009
  • Re: Difference between MSXML2.XmlHttp and Microsoft.XmlHttp ProgIDs

    @Nath-22 Remember MSXML is not tied to a particular browser version and can be updated independantly. I still think it's lack of good documentation - I can find no evidence that say, DOJO (for instance) is doing anything special with Msxml2.XMLHTTP.4.0 -- unless someone from Dojo (or any of the other js toolkits) wants to comment? Latest Version (1.2.3) // These are in order of decreasing likelihood; this will change in time. d._XMLHTTP_PROGIDS = [ 'Msxml2.XMLHTTP' , 'Microsoft.XMLHTTP'
    Posted to Client Side Web Development (Forum) by Wukfit on 1/28/2009
  • Re: Difference between MSXML2.XmlHttp and Microsoft.XmlHttp ProgIDs

    Hi there webjose, Just goes to show how crap/confusing MS documentaion is - posting to a 2yr old thread! I think the original question was more of a why do 'all' the Ajax Libraries test for MSXML2.XMLHttp.3.0, Microsoft.XMLHTTP, MSXML2.XMLHTTP when Microsoft.XMLHTTP will suffice? I stand by my original answer - lack of good documentation from MS. But the bigger question to ask is "is this really relevant any more?" - Do you still want to support outdated web browsers for this type
    Posted to Client Side Web Development (Forum) by Wukfit on 11/7/2008
  • Re: Difference between MSXML2.XmlHttp and Microsoft.XmlHttp ProgIDs

    @eric Hi Eric I just wanted to clarify something with you, are you saying that legacy browser support (e.g. IE 5.x) requires the use of both MSXML2.XMLHTTP and Microsoft.XMLHTTP? Cheers, Wukfit
    Posted to Client Side Web Development (Forum) by Wukfit on 8/17/2007
  • Re: Difference between MSXML2.XmlHttp and Microsoft.XmlHttp ProgIDs

    I wasn't implying that you were a beginner I've no idea what the level of knowledge/experience is of people posting to this forum - so please don't take offence. OK Just to back up my reasoning for why AJAX frameworks test for multiple versions of the progid... This snippet is taken from a recent version of the YUI (Yahoo) Library: YAHOO.util.Connect = { /** * @description Array of MSFT ActiveX ids for XMLHttpRequest. * @property _msxml_progid * @private * @static * @type array */ _msxml_progid
    Posted to Client Side Web Development (Forum) by Wukfit on 8/17/2007
  • Re: Difference between MSXML2.XmlHttp and Microsoft.XmlHttp ProgIDs

    OK I guess I'm not understanding the questions you want answered so I'll try to answer each of the questions in your initial post.... Q: Could someone explain me the difference between following version independent ProgIDs: MSXML2.XmlHttp and Microsoft.XmlHttp? A: There is no difference, Microsoft decided to change the namsepace from Microsoft to MSXML2 - they will both instantiate the same version of the MSXML object - which could be MSXML 2.0, MSXML 2.6 or MSXML 3.0 Q: Which one is preferable
    Posted to Client Side Web Development (Forum) by Wukfit on 8/13/2007
  • Re: Difference between MSXML2.XmlHttp and Microsoft.XmlHttp ProgIDs

    Just in case anyone else looks at this thread.... I think I understand your question - you're right from what I've read it's pointless testing for MSXML2.XmlHttp, Microsoft.XmlHttp (AND MSXML2.XmlHttp.3.0) as they will all point to the same version - and theres no way to tell which version this is. The 3 progids (MSXML2.XmlHttp, Microsoft.XmlHttp and MSXML2.XmlHttp.3.0) reference v2.x to v3 of MSXML, which would have been installed in "replace mode" (installing version 3 replaced
    Posted to Client Side Web Development (Forum) by Wukfit on 8/13/2007
Page 1 of 1 (7 items)