Having a generic solution/API for EPICS process database like you and Michael propose would be beneficial for other projects as well, ie PyDevice where a lot of people now use PyEpics when interfacing with PVs inside same or remote IOCs.
Not sure if I understand you fully...
The SNC produces C code, the EPICS process database APIs are in C.
The idea is that SNC code stops using CA and instead uses the existing APIs and mechanisms in Base to interface with records: i.e., reading, writing and setting up monitors.
For SNL state machines, things should not change too much. (I hope.) They would hook into the process database directly instead of having the IOC's CA server do it remotely.
It would remove SNC's dependency on CA and greatly simplify connection handling.
I don't think there would be any new APIs or mechanisms on the IOC - so I'm curious how that would be beneficial for Python code. (E.g., pyDevSup has a nice and powerful API to the EPICS process database.)
Cheers,
~Ralph
