| 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: Stream device - general concept how to use |
| From: | Christian Pauly via Tech-talk <tech-talk at aps.anl.gov> |
| To: | "Arnold, Ned D." <nda at anl.gov>, "Rivers, Mark L." <rivers at cars.uchicago.edu> |
| Cc: | "tech-talk at aps.anl.gov" <tech-talk at aps.anl.gov> |
| Date: | Thu, 16 Jul 2020 17:55:53 +0200 |
Thanks for the adviceLinking the set-records to the corresponding get-status records is indeed a very good idea.
Connecting all the get-records together via forward-links sounds a bit unpractical for maintenance. Maybe then its better to use a single (or nested if one is not enough) Fanout records for regular scanning of all status-records ?
I am still wondering why there is nothing foreseen to get prompt execution of a record (and its protocol) once its read via caget (prior to returning the result). This would be similar to the PP ProcessPassive flag mechanism when using input links.