Experimental Physics and Industrial Control System
|
--- Begin Message ---
Hi,
Along the lines of configuration and management, I was wondering what
the plans were for EPICS V4. Would it be possible to have a different
mechanism than a text-based startup file? I'm thinking out loud here,
but this is what I'm suggesting:
Have IOCCore boot as a generic kernel with a configuration and
management API (probably something other than CA). I don't know what
all can be loaded after the boot of the kernel, but it would be nice to
be able to at least send the DBD and DB configuration explicitly via a
deployment API. Perhaps even device/driver binaries can be loaded this way?
I've seen this technique become quite popular in the business middleware
arena. The JBOSS project (application server) now runs as a generic
kernel which grabs its configuration after boot. There is an extensive
config and management API which provides all sorts of meta-data, and
also allows for run-time re-configuration.
- Claude
--- End Message ---
- Navigate by Date:
- Prev:
V4 DB RecordCommon: Suggestion for alarmAckTransient (ACKT replacement) Ralph Lange
- Next:
Re: Fwd: Control System Data Access API Marty Kraimer
- Index:
2002
2003
2004
<2005>
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
- Navigate by Thread:
- Prev:
Re: V4 DB RecordCommon: Suggestion for alarmAckTransient (ACKT replacement) Marty Kraimer
- Next:
Re: Fwd: Control System Data Access API Marty Kraimer
- Index:
2002
2003
2004
<2005>
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
|
ANJ, 02 Feb 2012 |
·
Home
·
News
·
About
·
Base
·
Modules
·
Extensions
·
Distributions
·
Download
·
·
Search
·
EPICS V4
·
IRMIS
·
Talk
·
Bugs
·
Documents
·
Links
·
Licensing
·
|