[mapguide-internals] The Pinned Connection

[Leaf Li]

Harris,

Badreddine's description is absolutely right. MapGuide server will keep track of the association between (session,fsdid,connection). What I mean is that two pinned connections aren't allowed to created in one session for the same feature source. If users pass a different feature source id when calling MgFeatureService::PinConnection(), feature service will create pinned connection for current session and this feature source. 

Thanks,
Leaf Li

>Harris,
>
>You should be able to pin more than one connection per session. The new API takes a feature source id and an application can create any number of those ids and pin their associated connections. My >understanding is that the server will keep track of the association between (session,fsdid,connection). Even though the a fsid may refer to the same connection parameters as an existing fsid, if >PinConnection is called using the new fsid, then a new connection will be pinned. Of course, you can have a third fsid to the same data and decide not to pin the associated connection. In that case you >just grab a connection from the pool as you do today. I assume that pinned or not, the connection will stay around if a reader is still using it.
>
>Badreddine