Experimental Physics and
Industrial Control System

On Thursday 09 July 2009 09:17:11 Bruno Coudoin wrote:
>
> I also had this case in mind but this is handled internally by the CAS
> send process. If I understood it well, it just discards the new provided
> GDD if the Queue for a particular client is full. Anyway, the memory
> usage stay under control because the queue is limited.

If the CAS behavior is the same as the IOC's server, it should actually be 
discarding the most recent item on the queue to make way for the new data.  
That way if the data stream stops when the client gets to the end of the 
queue it will always see the final data value(s).

- Andrew
-- 
The best FOSS code is written to be read by other humans -- Harold Welte

References:

Detecting data lost from a subscriber Bruno Coudoin

RE: Detecting data lost from a subscriber Dalesio, Leo

RE: Detecting data lost from a subscriber Bruno Coudoin

Navigate by Date:

Prev: RE: Detecting data lost from a subscriber Bruno Coudoin

Next: Access to IO registers from user-space in recent Linux versions Mark Rivers

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 

Navigate by Thread:

Prev: RE: Detecting data lost from a subscriber Bruno Coudoin

Next: Proposed change to ASYN lockPort() Eric Norum

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