| 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: putNotify db links |
| From: | Andrew Johnson <[email protected]> |
| To: | Dirk Zimoch <[email protected]> |
| Cc: | EPICS <[email protected]> |
| Date: | Thu, 15 Aug 2013 11:12:39 -0500 |
Hi Dirk, On 08/15/2013 10:18 AM, Dirk Zimoch wrote:
Is it possible to make a database link wait for completion?
Not a regular link, but the "Async Soft Channel" output device supports that come with Base 3.14 do exactly that. In 3.15 we also provide input device supports which do process-get as well, which Marty had to do some major internal surgery to support. The facility is now called process-notify instead of put-notify as a result.
Now it would be nice to have "put notify" links, e.g:
field (LNK1, "A.PROC PN")
So that LNK2 is only processed when the whole LNK1 chain has finished
processing.
Unfortunately we can't do this for regular links because the API that record types call to do put and get operations on regular links doesn't provide for the necessary callback-on-completion which would allow for asynchronous operations like that. Making this something that could be configured on a per-link basis would require rewriting every record type to support such links.
- Andrew -- Advertising may be described as the science of arresting the human intelligence long enough to get money from it. -- Stephen Leacock