[AccessD] XML changes coming, XML 4.0 to be kill bitted in Oct 2007 but just in IE

There are many XML DOM parsers aside from Microsoft's not to mention SAX 
parsers.
However AJAX with MS IE, uses an XMLHTTP Active X to grab files.
XML is based on a series of WSC standards that are being released on a 
yearly basis.
like XSLT 2.0 or XPATH 2.0.  SQL 2005 SP2 installs XML 6.0
also Microsoft .NET Framework 3.0, Microsoft Visual Studio 2005,
and Windows SharePoint Services 3.0.

To get around crossbrowser problems using say Mozilla, you can use 
JavaScript
methods that have been around prior to AJAX. One I use is Sarissa.
A lot of these libraries are available for AJAX.
A cross-browser ECMAScript lib that helps with browser incompatibilities
in XMLHttpRequest/XML/XSLT/XPath along with some with some
useful utility methods. Just extract sarrissa.js

https://sourceforge.net/projects/sarissa/

How  to use
 http://www.yourhtmlsource.com/javascript/ajax.html#crossbrowser

A really simple cross browser java script

/* creates an XMLHttpRequest instance */
function createXmlHttpRequestObject()
{
// will store the reference to the XMLHttpRequest object
var xmlHttp;
// this should work for all browsers except IE6 and older
try
{
// try to create XMLHttpRequest object
xmlHttp = new XMLHttpRequest();
}
catch(e)
{
// assume IE6 or older
var XmlHttpVersions = new Array("MSXML2.XMLHTTP.6.0",
"MSXML2.XMLHTTP.5.0",
"MSXML2.XMLHTTP.4.0",
"MSXML2.XMLHTTP.3.0",
"MSXML2.XMLHTTP",
"Microsoft.XMLHTTP");
// try every prog id until one works
for (var i=0; i<XmlHttpVersions.length && !xmlHttp; i++)
{
try
{
// try to create XMLHttpRequest object
xmlHttp = new ActiveXObject(XmlHttpVersions[i]);
}
catch (e) {}
}
}
// return the created object or display an error message
if (!xmlHttp)
alert("Error creating the XMLHttpRequest object.");
www.PacktPub.com
13
else
return xmlHttp;
}
/*


Jim Lawrence wrote:

>Hi Marty:
>
>Excellent research as always. 
>
>Does this mean that there will be 2 versions of XML, MS's and everyone
>else's? AJAX is enough of an issue. 
>
>Jim
>
>-----Original Message-----
>From: accessd-bounces at databaseadvisors.com
>[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of MartyConnelly
>Sent: Monday, April 16, 2007 12:04 PM
>To: Access Developers discussion and problem solving
>Subject: [AccessD] XML changes coming, XML 4.0 to be kill bitted in Oct 2007
>but just in IE
>
>Just a heads up. You may want to upgrade to XML 6.0 in the future
>even just for the security fixes, never mind the new WSC XML standards
>introduced.
>
>MS are going to push out an IE specific kill-bit for MSXML4 in October 2007.
>
>http://blogs.msdn.com/xmlteam/archive/2007/03/12/msxml4-is-going-to-be-kill-
>bit-ed.aspx
>
>MSXML6 is included in Vista by default and MSXML 6.0 SP 1 is available for
>download for supported downlevel platforms from
>http://www.microsoft.com/downloads/details.aspx?FamilyID=d21c292c-368b-4ce1-
>9dab-3e9827b70604&displaylang=en
>
>MSXML 6.0 will be the means whereby support for new versions
>of XPath 2.0 and XSLT 2.0 make their way into the Visual Studio and
>Microsoft programming language environments, along with the brand new 
>XQuery 1.0.
>
>However one thing to check, MSXML 6.0 has removed support for XDR schemas
>but not XSD schemas.
>
>MSXML 4.0 will still be available via programming references
>
>* MSXML 3.0 has shipped with every supported Windows OS,
>so Microsoft professes to be "committed to keeping MSXML3 robust and
>stable but won't be adding any functional improvements."
>
>* MSXML 4.0 will be killed off some time between October and December of 
>2007,
>via a "kill bit" that applies only to Internet Explorer. The upshot of 
>this change is that
>applications will no longer be able to create MSXML4 objects in that 
>browser.
>Applications based on programming languages, such as C++, are not aware 
>of this kill bit
>and will continue to work with MSXML4. For a list of changes introduced 
>from MSXML4 and
>MSXML6, plus migration topics, see the blog entry entitled "Upgrading to 
>MSXML 6.0."
>
>MS are going to push out an IE specific kill-bit for MSXML4 in October. 
>More information here:
>
>http://blogs.msdn.com/xmlteam/archive/2007/03/12/msxml4-is-going-to-be-kill-
>bit-ed.aspx
>
>http://msdn2.microsoft.com/en-us/library/ms753751.aspx
>http://msdn2.microsoft.com/en-us/library/ms764692.aspx
>
>
>MS Notes.
>
>MSXML6 - Should be your first choice. This is the MSXML
>version that will be carried forward. MSXML6 shipped with Vista and we 
>are working
>on getting this in downlevel OS Service Packs
>
>MSXML3 - This has the advantage of having shipped with every supported OS .
>We are committed to keeping MSXML3 robust and stable but
>won't be adding any functional improvements.
>
>MSXML4 - This is in maintenance mode with a very high bar for fixes 
>approaching End of Life.
>
>MSXML 5 - Exclusively meant for Office. Do not take any dependencies on it.
>
>
>  
>

-- 
Marty Connelly
Victoria, B.C.
Canada