Hi,
I'm wondering how flexible BOY and its widgets are concerning
interprocess communication (IPC) protocols other than Channel Access.
We likely will use BOY for all our EPICS interfaces, and are considering
using it for our experiment control interfaces as well (i.e. for our
"ECS", following LHC nomenclature). Our experiment control and DAQ
systems use IPC protocols other than CA, including some home-grown ones
(e.g. the cMsg publish/subscribe package).
Can BOY accept IPC plugins? Is CA implemented as a plugin or something
analogous? Does BOY use a generic interface to connect to IPC packages
that we can implement ourselves using our other IPC packages? Or is CA
hard-wired in and difficult to disentangle from the core BOY code?
Any information and especially suggestions on how to proceed will be
appreciated.
Thanks,
--
Sincerely,
Elliott
================================================================================
Those raised in a morally relative or neutral environment will hold
no truths to be self-evident.
Elliott Wolin
Staff Physicist, Jefferson Lab
12000 Jefferson Ave
Suite 8 MS 12A1
Newport News, VA 23606
757-269-7365
================================================================================
- Replies:
- RE: BOY widgets and protocols other than Channel Access james.rowland
- Navigate by Date:
- Prev:
EPICS collaboration meeting Dirk Zimoch
- Next:
RE: BOY widgets and protocols other than Channel Access james.rowland
- Index:
1994
1995
1996
1997
1998
1999
2000
2001
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:
EPICS collaboration meeting Dirk Zimoch
- Next:
RE: BOY widgets and protocols other than Channel Access james.rowland
- Index:
1994
1995
1996
1997
1998
1999
2000
2001
2002
2003
2004
2005
2006
2007
2008
2009
2010
<2011>
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
|