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.
Yesterday when Peregrine, with help from Fritz Bartlett, suggested this
I sounded negative.
Thinking about it going home I started thing it was a nice idea. I am
always suprised when someone discovers a new use for something created
for a completely different reason. Since PUTF was created only to
support reprocessing a record if PACT is true when a dbPutField occurs,
this is what happened.
It is also a little scarry because it means that the original feature
must not be changed in such a way that it breaks the new usage. This is
prbably why my initial reaction was negative.
Marty Kraimer
- Replies:
- Re: Record processing knowledge of dbAccess context Peregrine McGehee
- References:
- RE: Record processing knowledge of dbAccess context J. Frederick Bartlett
- Re: Record processing knowledge of dbAccess context Peregrine M. McGehee
- Navigate by Date:
- Prev:
Problem starting StripTool JaSeong Ju
- Next:
Re: Record processing knowledge of dbAccess context Peregrine McGehee
- 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
- Navigate by Thread:
- Prev:
Re: Record processing knowledge of dbAccess context Peregrine M. McGehee
- Next:
Re: Record processing knowledge of dbAccess context Peregrine McGehee
- 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
|