Changes between Version 8 and Version 9 of MapGuideRfc19


Ignore:
Timestamp:
Apr 13, 2007, 1:13:33 PM (15 years ago)
Author:
brucedechant
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • MapGuideRfc19

    v8 v9  
     1= !MapGuide RFC 19 - Concurrent FDO provider connections =
     2
     3This page contains a change request (RFC) for the !MapGuide Open Source project. 
     4More !MapGuide RFCs can be found on the [wiki:MapGuideRfcs RFCs] page.
     5
     6
     7== Status ==
     8 
     9||RFC Template Version||(1.0)||
     10||Submission Date||Apr 13, 2007||
     11||Last Modified||Bruce Dechant [[Timestamp]]||
     12||Author||Bruce Dechant||
     13||RFC Status||Draft||
     14||Implementation Status||Pending||
     15||Proposed Milestone||1.2||
     16||Assigned PSC guide(s)||Robert Bray||
     17||'''Voting History'''||April 13, 2007||
     18||+1||||
     19||+0||||
     20||-0||||
     21||-1||||
     22 
     23== Overview ==
     24
     25The purpose of this RFC is to support a way to limit the # of concurrent FDO connections to a specific provider. By allowing for a limit to the # of concurrent FDO connections the server can support single threaded providers and any provider that has a limit on the # of client connections (ie: Oracle, etc...).
     26
     27== Motivation ==
     28
     29Currently, the server only supports FDO providers that support a thread-per-connection or better thread model. Although not ideal there is no support for single-threaded providers or for restriction the # of concurrent FDO connections. This needs to be addressed.
     30
     31== Proposed Solution ==
     32
     33
     34== Implications ==
     35
     36
     37
     38== Test Plan ==
     39
     40Test concurrent access to various FDO providers.
     41Test single threaded FDO provider, example GDAL.
     42
     43== Funding/Resources ==
     44
     45Autodesk to provide resources / funding.