2002 2003 2004 <2005> 2006 2007 2008 2009 2010 2011 2012 2013 2014 2015 2016 2017 2018 2019 2020 2021 2022 2023 2024 | Index | 2002 2003 2004 <2005> 2006 2007 2008 2009 2010 2011 2012 2013 2014 2015 2016 2017 2018 2019 2020 2021 2022 2023 2024 |
<== Date ==> | <== Thread ==> |
---|
Subject: | V4 Database Access |
From: | Ralph Lange <[email protected]> |
To: | EPICS Core Talk <[email protected]> |
Date: | Wed, 15 Jun 2005 16:47:12 +0200 |
Another thing that I recently found missing:I think we agreed to introduce APIs between the IOC database and the CA server that allow - other (network) servers to register with the database (as listeners being interested in getting events) - other (database kind of) things to register as a new provider of "records" (i.e. named DA property catalogs)
Where's the new thing (module, service, handler?) that provides these interfaces?
Seen from 3.14, this takes over some of the functionality that has been in the database and some from Channel Access. It should handle record name resolution and connection to DA interfaces (to handle requests coming in from servers). It should also work as an event handler (broker?) that software modules (like a server or the Vampire) can subscribe to and the database can post its events to that get distributed to the registered listeners.
I'm not sure about the design as all this definitely sounds like a local cut-down version of channel access. If we introduce client-specified monitor deadbands - should handling these deadbands by client be moved from CAS down into that layer to make it available for other transports/servers?
I'm not trying to impose anything here ... it's just that the Vampire needs to intercept db_post_event() and add more channels to the IOC record namespace, and I don't know at which level that would be done.
Cheers, Ralph