Hi John, John Snelson <[EMAIL PROTECTED]> writes:
> In XQilla the grammars are copied from the DOMBuilder to an > XMLGrammarPool owned by the DOMXPathExpression to make them accessible > in a thread safe manner. Looking at the DOM 3 specs, nothing is said > about the thread-safety of DOMXPathExpression - I think that I can > remove the copying if we agree that DOMXPathExpression should not be > thread-safe. I think it is ok to assume that a DOMXPathExpression instance is not thread-safe in the sense that it cannot be used concurrently from multiple threads without user-provided synchronization (this is also the case for other DOM nodes). On the other hand, it would be bad to disallow using independent DOMXPathExpression instances from multiple threads. Which case are you referring to? > Otherwise, I'm happy with the string pool syncing work-around. Yes, I think this is the easiest fix for the time being (I've already sent a patch to xqilla-users). Boris -- Boris Kolpackov, Code Synthesis Tools http://codesynthesis.com/~boris/blog Open source XML data binding for C++: http://codesynthesis.com/products/xsd Mobile/embedded validating XML parsing: http://codesynthesis.com/products/xsde --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
