|
Geos - multithreading and error handling: msg#00064gis.geos.devel
Is geos safe for multi-threading? What is the approach when using the C-API for error handling? I see that you can install an error handler and a notice handler. However, those functions are global. So in a multi-threaded app its easy to see how different threads could trigger these functions in an unexpected order causing the wrong error message to be returned to each thread. How have people dealt with this? Using thread-local storage? Or serializing there calls into GEOS? Or some other mechanism? Charlie
geos-devel mailing list geos-devel@xxxxxxxxxxxxxxxxxxxx http://geos.refractions.net/mailman/listinfo/geos-devel |
|
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| Previous by Date: | Assertions in CoordinateArraySequence: 00064, Charlie Savage |
|---|---|
| Next by Date: | Re: Swig Update and questions: 00064, strk |
| Previous by Thread: | Assertions in CoordinateArraySequencei: 00064, Charlie Savage |
| Next by Thread: | Re: Geos - multithreading and error handling: 00064, Mateusz Loskot |
| Indexes: | [Date] [Thread] [Top] [All Lists] |
| News | FAQ | advertise |