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 | 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: Network Accessable Types |
From: | Ralph Lange <[email protected]> |
To: | EPICS Core Talk <[email protected]> |
Date: | Tue, 26 Jul 2005 17:05:30 +0200 |
Kay-Uwe Kasemir wrote:
On Jul 26, 2005, at 05:49, Ralph Lange wrote:1. Learning the native type of data is part of the DA interface. The DA interface is purely about data and does not have any notion of network transport. An application may access things within a library or through shared memory using DA without any network involved.The application should see a data interface that allows random access: List the properties, learn that the 5th property is the "value", typed as some sort of number, then fetch it as a double. Ask for the "units" property as a string, ...
I don't see your point here, as all this is true for Data Access (assuming that the surveyor yields something comprehensive and /not/ just empty objects):
- The traverse methods will list properties and types (surveyor)- The find method will fetch a property by name (the viewer will convert it to the format of your local storage)
The knowledge that something is "the 5th" property in a catalog does not hold any information, as all access is only by property name/id. Of course your app may count and number properties any way it wants. (Data Access does not preclude you from counting properties. ;-)
Ralph