Changes between Version 18 and Version 19 of MapGuideRfc19

Timestamp:

Apr 20, 2007, 3:03:22 PM (17 years ago)

Author:

brucedechant

Comment:

--

MapGuideRfc19

@@ -11 +11 @@
 ||Last Modified||Bruce Dechant [[Timestamp]]||
 ||Author||Bruce Dechant||
-||RFC Status||Draft||
-||Implementation Status||Pending||
+||RFC Status||adopted||
+||Implementation Status||pending||
 ||Proposed Milestone||1.2||
 ||Assigned PSC guide(s)||Robert Bray||
-||'''Voting History'''||||
-||+1||||
-||+0||||
+||'''Voting History'''||April 20, 2007||
+||+1||Bob, Bruce, Jason, Tom||
+||+0||Paul||
 ||-0||||
 ||-1||||
@@ -23 +23 @@
 == Overview ==
 
-The purpose of this RFC is to support a way of limiting the # of concurrent FDO provider connections to a specific provider. By allowing for a way to limit the # of concurrent FDO provider connections the server can support single threaded providers and any provider that has a limit on the # of client connections (ie: Oracle, etc...).
+The purpose of this RFC is to support a way of limiting the # of concurrent FDO provider connections to a specific provider. 
 
 == Motivation ==
 
-Currently, the server only supports FDO providers that support a thread-per-connection or better thread model. Without implementing this RFC there will be no support for single-threaded providers or for limiting the # of concurrent FDO provider connections.
+By allowing for a way to limit the # of concurrent FDO provider connections the server can support single threaded providers and any provider that has a limit on the # of client connections (ie: Oracle, etc...).
 
 Note: The existing releases of !MapGuide did not check the provider thread model and subsequently allowed single-threaded providers to be used albeit in an unsafe manner.