Hi Andrew,
Thanks -- I'll gladly take all the advice you can give on this!
I find that if I create channels inside Python threads they do have
new contexts (that is other than the initial one), even without
asking. Doing
ca_create_context(); create-and-use-channels ; ca_context_destroy()
within a thread seems to work fine.
In order to have all processing done in one context, I have to
explicitly get the initial context in the main thread, and pass this
into each thread. That seems like extra work for the user. If
that's the recommendation, would it be reasonable to have ca.py make
sure to attach to the initial context (if needed) prior to any
processing?
Is there a use-case for multiple contexts on the client side?
Thanks,
--Matt Newville
- Replies:
- Re: PyEpics and Python threads Andrew Johnson
- References:
- PyEpics and Python threads Vigder, Mark
- RE: PyEpics and Python threads Vigder, Mark
- Re: PyEpics and Python threads Matt Newville
- Re: PyEpics and Python threads Andrew Johnson
- Navigate by Date:
- Prev:
Memory bank swap feature for SIS3301? Frank Hoeflich
- Next:
RE: Handling of String Array in CaChannel library Wang Xiaoqiang
- 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: PyEpics and Python threads Andrew Johnson
- Next:
Re: PyEpics and Python threads Andrew Johnson
- 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
|