Re: Newbie: CComBSTR limitation?
If you are constructing the XML, I suggest you forgo DOM
and dump it directly into a stream...
--
=====================================
Alexander Nickolov
Microsoft MVP [VC], MCSD
email: agnickolov@mvps.org
MVP VC FAQ: http://www.mvps.org/vcfaq
=====================================
"Vivek" <vivek@nospam.please.com> wrote in message
news:1158282620.967666@goodnews.cos.agilent.com...
Hi Brian,
I agree that this is not the best way of utilizing BSTRs. The only reason
for why it is being used is become a member function of the
IXMLDOMDocument (MSXML framework) object accepts only BSTR when attempting
to convert XML nodes into a string, which is then later dumped to a file.
If there was a method that allowed the user code to dump the contents to a
file or to an IStream interface directly, then I would certainly use it.
Unfortunately, this is the only way:
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/xmlsdk/html/31f7af53-6c3f-4a3e-a503-8aed9c4b270e.asp
Splitting the data up into chunks is currently not an option, since there
currently is no perceived way of doing this... If you can suggest
something better, than yes, I am willing to look into it. Thanks!
Regards,
Vivek
Brian Muth wrote:
Can I ask what your intention is with this enormous BSTR? What kind of
operation are you expecting to perform on it? I strongly suspect there is
a better path than the one you are on. (I think Alexander is likely to
agree there is probably BSTR-abuse going on.)
Brian