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: | [Fwd: EPICS V4 requirement ?] |
From: | Marty Kraimer <[email protected]> |
To: | [email protected] |
Cc: | Claude Saunders <[email protected]> |
Date: | Thu, 20 Oct 2005 06:46:08 -0500 |
--- Begin Message ---
Subject: EPICS V4 requirement ? From: Claude Saunders <[email protected]> To: [email protected], Andrew Johnson <[email protected]> Cc: Ned Arnold <[email protected]> Date: Wed, 19 Oct 2005 15:53:44 -0500 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 ---