| 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 2025 | 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 2025 |
| <== Date ==> | <== Thread ==> |
|---|
| Subject: | Re: Record processing knowledge of dbAccess context |
| From: | "Peregrine M. McGehee" <[email protected]> |
| To: | Marty Kraimer <[email protected]>, [email protected] |
| Date: | Thu, 08 Apr 2004 13:46:32 -0600 |
This should work (given the database design caveats). In the general case the answer is still "No".
Thanks, Peregrine
Peregrine M. McGehee wrote:
In which case a possible solution for a bidirectional record (without custom record types but with custom device support) is:
record A : input record with custom dev sup, scan PASSIVE record B : periodically scanned record, with FLNK to A
within A's read_xxx device support function: if PUTF true then grab VAL and write to hardware else read from hardware and write to VAL
This writes on demand from the CA client and reads periodically.
This should work but if anyone ever uses A in a different way, e.g. an output link is directed to it then it will fail.
Marty
-- Peregrine M. McGehee Sloan Digital Sky Survey LANL/LANSCE-8 and NMSU/Department of Astronomy (505) 667-3273; MS H820, LANL, Los Alamos, NM 87545