Hi Ralph,
On Thursday 08 January 2009 07:56:53 Ralph Lange wrote:
>
> RTYP is a pseudo field: When a read request for a "*.RTYP" PV comes in,
> the CA client library strips the ".RTYP" and converts it to a
> DBR_CLASS_NAME request.
Wrong, RTYP is one of two standard Record Attributes, pseudo-fields supported
by the database whose values are specific to the record type and can be set
(and new attributes created) using dbPutAttribute(). If the .RTYP handling
was an artifact of CA like you suggest I wouldn't be able to do this from the
ioc shell:
epics> dbgf mrk:stringinsyn.RTYP
DBR_STRING: "stringin"
Go read section 6.14 of the AppDevGuide. Attributes have been part of the IOC
since at least R3.13.0, just nobody uses them much...
> The only other case of CA-EPICSdb dependency (that I know of) is adding
> the ".VAL" extensionsto PVs without a field name. I don't know if this
> is done by the client or the server right now - it should be done on the
> server side for the same reasons.
Nothing explicitly adds .VAL to the PV name; when someone [currently RSRV, by
calling db_name_to_addr()] presents a PV name to dbNameToAddr() if the name
doesn't contain a field part it looks up the "VAL" field automatically. Thus
this is already done in the server.
- Andrew
--
The best FOSS code is written to be read by other humans -- Harold Welte
- Replies:
- Re: RTYP field through the PV Gateway Ralph Lange
- References:
- Re: RTYP field through the PV Gateway Ralph Lange
- Navigate by Date:
- Prev:
RE: RTYP field through the PV Gateway Jeff Hill
- Next:
Dates for a Codeathon at Brookhaven? Andrew Johnson
- 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: RTYP field through the PV Gateway Jeff Hill
- Next:
Re: RTYP field through the PV Gateway Ralph Lange
- Index:
2002
2003
2004
2005
2006
2007
2008
<2009>
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
|