Subversion Repository architecture

Hello !!!

I am a CVS user and was looking at subversion as an option down the line.
I have some questions about the future direction of subversion:
- Is the interface to the repository through static function calls or
through an abstraction layer using shared libraries?
     I would like to have the repository in a database. Best way to get
there will be to:
     . Implement an interface library to the repository.
     . This library should use dlopen to open a shared library that will
have the core routines for the repository interface
     This implies that you could have the repository in a database, or
normal files, or anything else. (Even RCS)
     This feature may make it easier for CVS users to migrate

- Would there be a Visual Studio Plug In?

- Would there be an Oracle Developer Plug In?

Thanks

----
Saad Ahmad
Oracle Practice Leader
Oracular, Inc.
(920)303-0470 x609
sahmad@oracular.com
http://www.oracular.com
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org