Is this for MapScript? Should really let Tamas chime in. A single mapObj instance is modified during the course of a request once ingested from the mapfile. For example, it holds a populated label cache and other changes made after it is loaded specific to a request. So I guess that means one mapObj per thread.
From: kelly elton [mailto:[email protected]] Sent: Thursday, November 05, 2015 4:35 PM To: Lime, Steve D (MNIT) <[email protected]>; [email protected] Subject: Re: [mapserver-users] Thread Safety To be sure, are you saying I can use a single map object for multiple threads, or will I need to have one map object per thread? What would you suggest? On Thu, Nov 5, 2015 at 5:33 PM Lime, Steve D (MNIT) <[email protected]<mailto:[email protected]>> wrote: You should be fine. I believe there are locks (mutex) around places where this is known to be a problem. I’ve never heard user reports of issues in this regard. Steve From: mapserver-users [mailto:[email protected]<mailto:[email protected]>] On Behalf Of kelly elton Sent: Thursday, November 05, 2015 4:07 PM To: [email protected]<mailto:[email protected]> Subject: [mapserver-users] Thread Safety Say....if I have two processes using the mapserver dll, are they going to conflict? I'm noticing on the website it says "OGR layers: use unsafe CPL services"...In my map file I have 'CONNECTIONTYPE OGR'....what I do with the map object is project, and then draw to png, and that's about it....this isn't thread safe then? What about if I have multiple map objects, one per thread....is that thread safe?
_______________________________________________ mapserver-users mailing list [email protected] http://lists.osgeo.org/mailman/listinfo/mapserver-users
