On 10/24/07, Daniel Veillard <[EMAIL PROTECTED]> wrote:
> On Wed, Oct 24, 2007 at 09:10:19PM +0530, Senthil Nathan wrote:
> >
> >Hi All,
> >
> >I was reading through the api's for locking the xml tree and checked
> >that,
> >
> >
> >
> >xmlMutexLock() is used to lock a libxml2 tok
On 23 Oct 21:21, Callum Gibson wrote:
}On 23 Oct 17:39, [EMAIL PROTECTED] wrote:
}}>The only consideration is that I probably need to get some clearance
}}>from my work to release the code. Hopefully there shouldn't be any problem
}}>there since there is no business-related intellectual property in
Hi,
We are looking for a way to process XPATH expressions on very large xml
documents. Because of the size of the documents, we like to use stream
processing something along the lines of XPathReader from MS. Searching the
archive, we found we could possibly use xmlPatternCompile along wi
> No. There is no locking in place in libxml2 for shared trees. One tree
> per thread or you manage your own locking.
>
> Daniel
>
Don't you mean "one THREAD per TREE" - I would think that one thread could
have multiple trees without problem, it would be multiple threads frobbing
the same tree
On Wed, Oct 24, 2007 at 09:10:19PM +0530, Senthil Nathan wrote:
>
>Hi All,
>
>I was reading through the api's for locking the xml tree and checked
>that,
>
>
>
>xmlMutexLock() is used to lock a libxml2 token.
>
>xmlMutexUnlock() is used to unlock a libxml2 token.
>
>
Hi All,
I was reading through the api's for locking the xml tree and checked that,
xmlMutexLock() is used to lock a libxml2 token.
xmlMutexUnlock() is used to unlock a libxml2 token.
xmlNewMutex() is used to allocate a libxml2 token struct for use in
synchronizing access to data.
Would like to kn
On Wed, Oct 24, 2007 at 11:07:21AM +0200, Dominik Raddatz wrote:
> Hi,
>
> the following statement seems somewhat slow:
>
> xmlNodePtr myNode;
> xmlChar *myText;
> ...
> xmlNewChild(myNode, NULL, BAD_CAST "description", BAD_CAST myText);
>
> takes about 25 ms when myText is 50kB; profiling sugge
Hi,
the following statement seems somewhat slow:
xmlNodePtr myNode;
xmlChar *myText;
...
xmlNewChild(myNode, NULL, BAD_CAST "description", BAD_CAST myText);
takes about 25 ms when myText is 50kB; profiling suggests it wastes much time
using "xmlStrlen()".
the comparable statements
xmlNodePtr
