Home. 
.

transparent

transparent

transparent

Altova Mailing List Archives


Re: IXMLDOMDocument::Load long pathname support

From: "Sam Hobbs" <samuel@------.--.---_------_------_--_----->
To: NULL
Date: 6/11/2008 3:50:00 PM

"Martin Honnen" <mahotrash@y...> wrote in message 
news:%23jUbI49yIHA.3972@T......
> mohit.jha@g... wrote:
>> 4.0
>
> The MSXML SDK says that load takes a URL as a string and I can't believe 
> that it fails if the URL is longer than 256 characters.
> What value exactly do you pass to the load method?
> What error do you get?
> Have you tried to use a file: URL e.g.
> file:///C:/dir/subdir/subsubdir/file.xml?
>
>
> -- 
>
> Martin Honnen --- MVP XML
> http://JavaScript.FAQTs.com/


Probably the limitation is a Windows limitation. The VC header stdlib.h has 
the following define:

    #define _MAX_PATH   260 /* max. length of full pathname */

The comment says that it is for "Sizes for buffers used by the _makepath() 
and _splitpath() functions." but that symbolic name is used frequently in 
the Windows samples. The value 256 or 260 is documented somewhere as the 
maximum size of a Windows filename without using the "UNC" (Universal Naming 
Code) format. I think the sample file URL above does not use the UNC format 
but I am not sure.





transparent
Print
Mail
Like It
Disclaimer
.

These Archives are provided for informational purposes only and have been generated directly from the Altova mailing list archive system and are comprised of the lists set forth on www.altova.com/list/index.html. Therefore, Altova does not warrant or guarantee the accuracy, reliability, completeness, usefulness, non-infringement of intellectual property rights, or quality of any content on the Altova Mailing List Archive(s), regardless of who originates that content. You expressly understand and agree that you bear all risks associated with using or relying on that content. Altova will not be liable or responsible in any way for any content posted including, but not limited to, any errors or omissions in content, or for any losses or damage of any kind incurred as a result of the use of or reliance on any content. This disclaimer and limitation on liability is in addition to the disclaimers and limitations contained in the Website Terms of Use and elsewhere on the site.

.
.

transparent

transparent