[ 
https://issues.apache.org/jira/browse/XERCESC-1737?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12520597
 ] 

Scott Cantor commented on XERCESC-1737:
---------------------------------------

I thought the same thing (about the need to modify DOMDocument), so I'm in 
agreement that we should skip it.

As for my application, these are documents created from network protocol 
messages and can't share a document to start with, the parser doesn't allow you 
to specify the document to parse into. Without adoptNode support, moving 
fragments to a common document is a copy operation, and that's not efficient 
either, but it might be workable, I'll take a look.

My code no longer caches any XML in DOM form, but I can't make that change on 
the affected branch.


> Patches for the 2.8.0 release
> -----------------------------
>
>                 Key: XERCESC-1737
>                 URL: https://issues.apache.org/jira/browse/XERCESC-1737
>             Project: Xerces-C++
>          Issue Type: Improvement
>            Reporter: Boris Kolpackov
>         Attachments: heap-v2.patch, heap.patch, https.patch, 
> patches-2.7.tar.gz
>
>
> I have prepared a patch for the following issues:
> * Support for g++ on AIX and HP-UX.
> * Auto-detection of aCC6 vs aCC3 in runConfigure.
> * Verbose mode (gmake VERBOSE=1)
> * Changed optimization level for GNU/Linux from -O to -O2
> * Fixes for 64 bit and SO_NAME options.
> * Project files for VS 2005.
> * Support for 64 bit Windows build.
> * Optimized DOM parsing (25-30% improvement).
> It consists of the following parts:
> ChangeLog        - description of the changes.
> xerces-2.7.patch - patch against the current xerces-2.7 branch
> VC8              - MSVC8 project files, should be copied to Projects/Win32/
> I have tested this code with most of the platforms mentioned in the
> "Xerces-C++ 2.8.0 release plan" email I send the other day.
> I would appreciate it if one of the Xerces-C++ developers review and
> commit this patch.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to