Subversion integration

I know there is quite a bit of activity going on in the web dav plugin , but what they are doing isn't exactly what I need for my organization.
We have standardized on subversion for configuration management for all our projects.
We are also looking at moving all the stuff that has accumulated on windows file shares into svn, and allowing non developers to connect via Web Dav (Windows Web Folders).
I have been trying to get management approval to move to install Confluence as a knowledge management tool, in part to clean up all the "stuff" we have lying around the place.
But having attachments stored in Confluence's own proprietary file store doesn't help the situation, in terms of consolidating where stuff gets stored. Especially when all our project plans state that all project artefacts shall be stored in subversion - except Jira issues of course
What would be ideal is having subversion as a back end to confluence. I.e. when you create a space, you give confluence a svn url of where to store content. Confluence then uses the svn repository to store and version all content, including the page as a text file, and attachments as files. This would automatically provide versioning through the normal svn features.
Confluence would have to poll the svn log to detect changes that have been made to the content and attachments through the svn or web dav interface. I don't know whether it would be best for Confluence to still store a copy of the page content or not - but in any case SVN would be the authoratative data store.

This would provide the following benefits:
1. All project content stored in the one CM repository, version controlled etc.
2. Nice web (Confluence) interface to the CM repository for non techy staff
3. Automatic web-dav functionality through SVN for people who still want to use it like a file share. This also makes importing content into Confluence/SVN drag and drop once web dav is mounted as a web folder

Oh and how about storing Jira issues in subversion as well