Hi,
+-From: Dan Shinton <d...@shinton.net> ----
|_Date: Tue, 22 Feb 2011 09:21:49 -0500 __
|
|My concern is the getRecipient() call; which simply returns the value of
|the member variable "recipient". In the case of the above code, the running
|thread is waiting for the async callback thread to call setRecipient() to
|signal that the response was received.
|Since thread A is waiting on the recipient variable to be mutated by thread
|B, shouldn't recipient be volatile to ensure thread A sees the change?
I agree with you.
It should be volatile, and will be in the next release.
Sincerely,
--
Atsuhiko Yamanaka
JCraft,Inc.
1-14-20 HONCHO AOBA-KU,
SENDAI, MIYAGI 980-0014 Japan.
Tel +81-22-723-2150
+1-415-578-3454
Skype callto://jcraft/
Twitter: http://twitter.com/ymnk
------------------------------------------------------------------------------
Free Software Download: Index, Search & Analyze Logs and other IT data in
Real-Time with Splunk. Collect, index and harness all the fast moving IT data
generated by your applications, servers and devices whether physical, virtual
or in the cloud. Deliver compliance at lower cost and gain new business
insights. http://p.sf.net/sfu/splunk-dev2dev
_______________________________________________
JSch-users mailing list
JSch-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jsch-users
