Changes between Initial Version and Version 1 of Ticket #6548, comment 3


Ignore:
Timestamp:
Jun 19, 2016, 11:00:19 PM (8 years ago)
Author:
glindsay

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #6548, comment 3

    initial v1  
    99Yep I completely agree that mapserver should not be aware of any driver specific implementation details.
    1010
    11 It would be better if you could somehow configure the connection lifestyle e.g transient, singleton and thread (refcount), so that the end user has complete control over when connections are closed.
    12 I am not sure about the best way that this could be done... maybe through an option in the 'PG:' connection string?
     11It would be better if you could configure the connection lifestyle explictly e.g transient, singleton or thread (e.g using a reference counter), so that the end user has complete control over when connections are open and closed.
     12Maybe a new 'lifestyle' option could be included in the 'PG:' connection string (which would be consistent with the way that the 'mode' option is handled).
    1313
    14 The Map Server Connection Pooling (mappool.c) allows different lifestyles to be configured and uses a reference counter to close off connections.
     14For reference, the Map Server Connection Pooling (mappool.c) allows different lifestyles to be configured and uses a reference counter to close off shared connections.