| Version 9 (modified by , 18 years ago) ( diff ) |
|---|
MapGuide RFC 19 - Concurrent FDO provider connections
This page contains a change request (RFC) for the MapGuide Open Source project. More MapGuide RFCs can be found on the RFCs page.
Status
| RFC Template Version | (1.0) |
| Submission Date | Apr 13, 2007 |
| Last Modified | Bruce Dechant Timestamp |
| Author | Bruce Dechant |
| RFC Status | Draft |
| Implementation Status | Pending |
| Proposed Milestone | 1.2 |
| Assigned PSC guide(s) | Robert Bray |
| Voting History | April 13, 2007 |
| +1 | |
| +0 | |
| -0 | |
| -1 |
Overview
The 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...).
Motivation
Currently, 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.
Proposed Solution
Implications
Test Plan
Test concurrent access to various FDO providers. Test single threaded FDO provider, example GDAL.
Funding/Resources
Autodesk to provide resources / funding.
