Return-Path: Delivered-To: apmail-incubator-river-dev-archive@minotaur.apache.org Received: (qmail 5101 invoked from network); 31 Jan 2011 03:43:16 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 31 Jan 2011 03:43:16 -0000 Received: (qmail 4580 invoked by uid 500); 31 Jan 2011 03:43:15 -0000 Delivered-To: apmail-incubator-river-dev-archive@incubator.apache.org Received: (qmail 3748 invoked by uid 500); 31 Jan 2011 03:43:13 -0000 Mailing-List: contact river-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: river-dev@incubator.apache.org Delivered-To: mailing list river-dev@incubator.apache.org Received: (qmail 3589 invoked by uid 99); 31 Jan 2011 03:43:12 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 31 Jan 2011 03:43:12 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=5.0 tests=RCVD_IN_DNSWL_NONE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of pats@acm.org designates 209.86.89.62 as permitted sender) Received: from [209.86.89.62] (HELO elasmtp-dupuy.atl.sa.earthlink.net) (209.86.89.62) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 31 Jan 2011 03:43:03 +0000 Received: from [70.230.203.179] (helo=[192.168.1.102]) by elasmtp-dupuy.atl.sa.earthlink.net with esmtpa (Exim 4.67) (envelope-from ) id 1Pjkf4-0000cM-SF for river-dev@incubator.apache.org; Sun, 30 Jan 2011 22:42:43 -0500 Message-ID: <4D462FAD.2000707@acm.org> Date: Sun, 30 Jan 2011 19:42:37 -0800 From: Patricia Shanahan User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.2; en-US; rv:1.9.2.13) Gecko/20101207 Thunderbird/3.1.7 MIME-Version: 1.0 To: river-dev@incubator.apache.org Subject: Question about JavaSpaces functionality Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-ELNK-Trace: 9a090983a806273c061ba25959e76cc985338a7d01cb3b6a7e972de0d01da940e2d85ab751f357ab45a20aa26b51dc9c350badd9bab72f9c350badd9bab72f9c X-Originating-IP: 70.230.203.179 X-Virus-Checked: Checked by ClamAV on apache.org Suppose thread A writes an item to a JavaSpace, thread B attempts to read it, and A's call to the space's proxy write method happens-before B's call to the space's proxy read method. There are no transactions involved Should the read always succeed? In other words, should a happens-before relationship between two actions in a client imply a corresponding happens-before relationship between the corresponding actions in the actual space, without depending on transaction semantics? This question affects whether I'm working on a bug in outrigger or in one of its tests. Thanks for any information. Patricia