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 | 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 |
<== Date ==> | <== Thread ==> |
---|
Subject: | Re: Devices Which Send Unsolicited Messages |
From: | Eric Norum <[email protected]> |
To: | EPICS tech-talk <[email protected]> |
Cc: | Steven Banks <[email protected]> |
Date: | Fri, 4 Aug 2006 08:02:40 -0500 |
I'd handle this situation by starting a worker thread from the driver initialization routine. The worker thread would enter a loop calling read() and whenever a complete message had been received, using the standard AYSN method of reporting an interrupt. This would kick off record processing which would process the results obtained by the worker thread.
-- Eric Norum <[email protected]> Advanced Photon Source Argonne National Laboratory (630) 252-4793 |