Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Thread safety of libcitygml #23

Open
GoogleCodeExporter opened this issue Apr 8, 2015 · 2 comments
Open

Thread safety of libcitygml #23

GoogleCodeExporter opened this issue Apr 8, 2015 · 2 comments

Comments

@GoogleCodeExporter
Copy link

This is more a question than a problem:

Are you aware of any issue that prevents libcitygml to be used  in a threaded 
context (e.g. multiple parsing threads in parallel).

Kind regards,
Jan

Original issue reported on code.google.com by [email protected] on 29 Jul 2011 at 1:43

@GoogleCodeExporter
Copy link
Author

If the xml library is ok for such a context everything should be ok in 
libictygml EXCEPT the tesselator which may be a problem because it is managed 
as a singleton to avoid the creation of multople GLU tesselation objects. So 
may be we could associate a tesselator per parser...
Any ideas or suggestions?
Regards,
Joachim

Original comment by [email protected] on 29 Jul 2011 at 1:55

  • Changed state: Accepted

@GoogleCodeExporter
Copy link
Author

After having done a test with multithreaded parsing it seems to be a good idea 
to synchronize the calls to initialize and terminate in the parser. The loading 
failed there once at my tests. 

Maybe you should have a look at 
http://xerces.apache.org/xerces-c/faq-parse-3.html at the question "Is it OK to 
call the XMLPlatformUtils::Initialize/Terminate pair of routines multiple times 
in one program?"

Is the tesselator per parser a big issue to do ? Should i have a look at it ?

Original comment by [email protected] on 30 May 2012 at 11:32

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant