[mapguide-internals] MapGuide RFC 65 - ACE 5.6 upgrade is ready for review

[Jason Birch]

Looks like one of the locks is still there:

http://trac.osgeo.org/mapguide/browser/branches/2.1/MgDev/Server/src/Services/Mapping/MappingUtil.cpp#L675

Was there something else in there limiting the raster provider to a single connection?

Jason

-----Original Message-----
From: Trevor Wekel
Sent: Thursday, June 04, 2009 1:35 PM
To: MapGuide Internals Mail List
Subject: RE: [mapguide-internals] MapGuide RFC 65 - ACE 5.6 upgrade is ready for review

Big giant locks would certainly affect multi-core scalability.  I know Bruce did a whole ton of work on the Fdo connection management in MapGuide to improve Gdal threading issues.  I don't know if the big giant lock went it.

-----Original Message-----
From: Traian Stanev
Sent: Thursday, June 04, 2009 2:15 PM
To: MapGuide Internals Mail List
Subject: RE: [mapguide-internals] MapGuide RFC 65 - ACE 5.6 upgrade is ready for review

While this is true, don't we also have the big giant lock in the code, which makes sure that if you have rasters for example (where I/O matters), you will only be working on one request at a time anyway?