[
https://issues.apache.org/jira/browse/XERCESC-1821?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12615768#action_12615768
]
Scott Cantor commented on XERCESC-1821:
---------------------------------------
I'm not sure (a) is a big deal. There are plenty of things people just know not
to do while parsing, this would be one of them. Most applications with this
requirement have a clearly defined startup phase that doesn't require
synchronization with the actual worker threads.
Given that, (b) is a non-issue.
I'm not sure about (c), and if you have any way to change the value, it can't
be const, so didn't you already lose that?
Anyway, while I can live with the 16K, I don't like it much and would love a
way to configure it to use 8k in my application in one spot.
> Configurable kInitialHeapAllocSize in xerces
> ---------------------------------------------
>
> Key: XERCESC-1821
> URL: https://issues.apache.org/jira/browse/XERCESC-1821
> Project: Xerces-C++
> Issue Type: Improvement
> Components: DOM
> Environment: All OS
> Reporter: george
> Priority: Minor
> Fix For: 3.0.0
>
>
> The default DOM initial heap size is 16k in the latest release (earlier
> release was 64k). this number could be still too big or too small for some
> system.
> The idea is to make the following parameters configurable in the constructor
> via a singleton read function.
> static XMLSize_t kInitialHeapAllocSize = 0x4000;
> static XMLSize_t kMaxHeapAllocSize = 0x20000;
> static XMLSize_t kMaxSubAllocationSize = 0x1000; // Any request for more
> bytes
> Now the question is if you think this is a valuable suggestion? I have a
> working code and would like to share if you think it worth the effort.
> Cheers
> George
--
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]
