Windows Workflow：自定义持久性服务，相同的架构和逻辑？

So I've been using the Windows Workflow default SQL persistence service that handles everything on its own with no fuss. Now, one of the environments I deploy to does not have direct access to the database; it pushes stored procedure calls through a web service over a proxy for added security. This of course does not please the SQL persistence gods, though I'd like to be able to leverage it from that environment. So really the only difference I have between the default behavior and potentially the one I code for our environment would be another way of calling the stored procedures: remotely instead of direct access (the web service shuffles datasets back and forth).So I've been using the Windows Workflow default