SHP provider only does SHP compression in the destructor of last live SHP connection.

[StevenXu]

Now SHP provider only does SHP compression in the destructor of last live SHP connection. Assume that there are two SHP connection to two difference SHP folder at the same time, and user delete something via the first SHP connection, and then close the first SHP connection, but remains the second SHP connection live. So the first SHP connection have no chance to do SHP compression any more, even the user close the second compression later.

[StevenXu]

As Dan Stoica said:

The situation can be fixed easily by creating a global array of strings that holds the open connections (i.e. the folder names). Each time a connection is open a new entry is added. Each time a connection is closed, do a look up in the array and: --Remove a matching entry --If no one left with the same name then do compression if the case.

[waltweltonlair]

Fix submitted to 3.4 stream with submission r5114.

[StevenXu]

However, this fix is fewer aggressive than Dan's idea by refining the granularity of ref counter to ShpFileSet , that means, the reference counter std::map was used against every opened file set rather than every opened SHP connection.

[StevenXu]

Fix submitted to trunk stream with submission ​r5111