Return-Path: Delivered-To: apmail-cayenne-user-archive@www.apache.org Received: (qmail 52313 invoked from network); 13 Feb 2009 05:28:55 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 13 Feb 2009 05:28:55 -0000 Received: (qmail 93518 invoked by uid 500); 13 Feb 2009 05:28:54 -0000 Delivered-To: apmail-cayenne-user-archive@cayenne.apache.org Received: (qmail 93506 invoked by uid 500); 13 Feb 2009 05:28:54 -0000 Mailing-List: contact user-help@cayenne.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@cayenne.apache.org Delivered-To: mailing list user@cayenne.apache.org Received: (qmail 93495 invoked by uid 99); 13 Feb 2009 05:28:54 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 12 Feb 2009 21:28:54 -0800 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of ari@ish.com.au designates 59.167.240.32 as permitted sender) Received: from [59.167.240.32] (HELO fish.ish.com.au) (59.167.240.32) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 13 Feb 2009 05:28:45 +0000 Received: from ip-132.ish.com.au ([203.29.62.132]:49669) by fish.ish.com.au with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.69) (envelope-from ) id 1LXrH1-0003mG-1Q for user@cayenne.apache.org; Fri, 13 Feb 2009 17:11:39 +1100 Message-Id: <51C00326-03EC-456D-9CA5-2AB49A9B27D4@ish.com.au> From: Aristedes Maniatis To: user@cayenne.apache.org In-Reply-To: Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Apple Message framework v930.3) Subject: Re: Commits not visible across contexts in ROP Date: Fri, 13 Feb 2009 16:28:11 +1100 References: X-Mailer: Apple Mail (2.930.3) X-Virus-Checked: Checked by ClamAV on apache.org On 13/02/2009, at 3:30 PM, Tarik Cherkovi wrote: > Hi,I just had a strange behavior from ROP and maybe missing > something basic. > I have multiple clients connecting to the same server, and when one > of them > performs a commit, the changes are not visible to the other > client(s). Is > there a way to make all remote contexts? You'll need to implement that behaviour yourself. Obviously the simplistic approach is to refresh all caches and queries on the remote client before you use data where freshness is important. The problem isn't a trivial one. If you have a bunch of clients on different subnets, they can't necessarily pass events directly to each other using JMS or something similar. So the server needs to be responsible for holding a list of update events which are then passed out to clients upon request. You could implement something with SnapshotEvents [1] which are passed either directly between clients (if they have direct access to each other) or via the server as an intermediary. Personally I didn't get much further than identifying a couple of libraries such as Apache Mina and Apache ActiveMQ which might be useful in such an implementation. But I am keen on implementing something for our own applications, if only we had more time.... Ari [1] http://cayenne.apache.org/doc/object-caching.html --------------------------> ish http://www.ish.com.au Level 1, 30 Wilson Street Newtown 2042 Australia phone +61 2 9550 5001 fax +61 2 9550 4001 GPG fingerprint CBFB 84B4 738D 4E87 5E5C 5EFA EF6A 7D2E 3E49 102A