Changes between Version 3 and Version 4 of MapGuideRfc86

Timestamp:

Sep 24, 2009, 6:49:56 PM (15 years ago)

Author:

leaf

Comment:

--

MapGuideRfc86

@@ -23 +23 @@
 == Overview ==
 
-This proposal is to extend MapGuide Feature Service so that calls to Feature Service can use the same FDO connection to avoid some unexpected errors. The solution is to add two methods BindConnection(MgResourceIdentifier featureSourceId) and UnbindConnection(MgResourceIdentifier featureSourceId) so that users are able to bind/unbind an FDO connection to the current user session. 
+This proposal is to extend MapGuide Feature Service so that calls to Feature Service can use the same FDO connection to avoid some unexpected errors. The solution is to add two methods BindConnection(!MgResourceIdentifier featureSourceId) and UnbindConnection(!MgResourceIdentifier featureSourceId) so that users are able to bind/unbind an FDO connection to the current user session. 
 
 == Motivation ==
@@ -32 +32 @@
 == Proposed Solution ==
 
-In this RFC, we extend Feature Service to add the ability to use the same FDO connection for calls to Feature Service. The following two methods will be added to class MgFeatureService to allow users to bind/unbind an FDO connection to the current session. Method BindConnection(...) will select an FDO connection from FDO connection pool for the specified feature source if there is one FDO connection available. Otherwise, create a new FDO connection and add it to FDO connection pool. Then this FDO connection is bound to current session. It means this FDO connection becomes an exclusive connection and can’t be used by other sessions. Since then, any call to Feature Service for the feature source and the session, which needs an FDO connection, will always use the bound FDO connection till users call method UnbindConnection(...) to unbind this FDO connection.
+In this RFC, we extend Feature Service to add the ability to use the same FDO connection for calls to Feature Service. The following two methods will be added to class !MgFeatureService to allow users to bind/unbind an FDO connection to the current session. Method !BindConnection(...) will select an FDO connection from FDO connection pool for the specified feature source if there is one FDO connection available. Otherwise, create a new FDO connection and add it to FDO connection pool. Then this FDO connection is bound to current session. It means this FDO connection becomes an exclusive connection and can’t be used by other sessions. Since then, any call to Feature Service for the feature source and the session, which needs an FDO connection, will always use the bound FDO connection till users call method !UnbindConnection(...) to unbind this FDO connection.
 
 {{{