Return-Path: Delivered-To: apmail-jakarta-turbine-jcs-user-archive@www.apache.org Received: (qmail 81314 invoked from network); 13 Oct 2004 12:16:51 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur-2.apache.org with SMTP; 13 Oct 2004 12:16:51 -0000 Received: (qmail 31765 invoked by uid 500); 13 Oct 2004 12:16:50 -0000 Delivered-To: apmail-jakarta-turbine-jcs-user-archive@jakarta.apache.org Received: (qmail 31733 invoked by uid 500); 13 Oct 2004 12:16:50 -0000 Mailing-List: contact turbine-jcs-user-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Turbine JCS Users List" Reply-To: "Turbine JCS Users List" Delivered-To: mailing list turbine-jcs-user@jakarta.apache.org Received: (qmail 31700 invoked by uid 99); 13 Oct 2004 12:16:49 -0000 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests=RCVD_BY_IP,SPF_HELO_PASS,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (hermes.apache.org: domain of tcocks@gmail.com designates 64.233.170.198 as permitted sender) Received: from [64.233.170.198] (HELO mproxy.gmail.com) (64.233.170.198) by apache.org (qpsmtpd/0.28) with ESMTP; Wed, 13 Oct 2004 05:16:49 -0700 Received: by mproxy.gmail.com with SMTP id 80so250363rnk for ; Wed, 13 Oct 2004 05:16:44 -0700 (PDT) Received: by 10.38.8.80 with SMTP id 80mr2031425rnh; Wed, 13 Oct 2004 05:16:44 -0700 (PDT) Received: by 10.38.206.21 with HTTP; Wed, 13 Oct 2004 05:16:44 -0700 (PDT) Message-ID: Date: Wed, 13 Oct 2004 13:16:44 +0100 From: Tim Cocks Reply-To: mail@timcocks.co.uk To: turbine-jcs-user@jakarta.apache.org Subject: Cannot work out how to get push working Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N All, We have JCS working in a pull configuration, with several clients consulting the master cache when they need to. We would like to change this to push, but have yet to manage it. We have tried setting 'RemoveUponRemotePut' to 'false', as the documentation appears to suggest, to no avail. We also investigated doing it by clustering, but came to the conclusion it was inappropriate for our needs. I'd be grateful if someone could explain the basic steps required to make JCS push instead of pull, and/or supply some simple configuration files. We are running a version of JCS checked out of Turbine's CVS repository yesterday. Tim Cocks --------------------------------------------------------------------- To unsubscribe, e-mail: turbine-jcs-user-unsubscribe@jakarta.apache.org For additional commands, e-mail: turbine-jcs-user-help@jakarta.apache.org