On 3/24/09 14:43 , "GaryCarr" <[email protected]> wrote:
> Are there any limitations that apply to one, and not the other?
Other differences:
When you close a JNI JCA channel, that's it.
CAJ will send a final value update to indicate that
the channel is now invalid, in case you registered monitors.
When you create duplicate channels like this
final Channel ch1 = jca_context.createChannel("fred", conn_callback);
final Channel ch2 = jca_context.createChannel("fred", conn_callback);
JNI JCA will give you 2 different ones,
while CAJ, within the same context, you will return
the same, i.e. ch2 == ch1.
If you then later clean up like this
ch2.destroy();
ch1.destroy();
you get a problem in CAJ because ch2.destroy actually
destroys both.
==> To be compatible, you do your own reference counting,
keep a hash of used channel names.
-Kay
- References:
- JCA2 vs CAJ GaryCarr
- Navigate by Date:
- Prev:
Re: JCA2 vs CAJ Kasemir, Kay
- Next:
Fonts for Probe under Scientific Linux Schoeneburg, Bernd
- 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: JCA2 vs CAJ Kasemir, Kay
- Next:
Re: JCA2 vs CAJ Matej Sekoranja
- 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
|