Return-Path: Delivered-To: apmail-hadoop-zookeeper-user-archive@locus.apache.org Received: (qmail 86233 invoked from network); 7 Jan 2009 04:55:39 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 7 Jan 2009 04:55:39 -0000 Received: (qmail 5294 invoked by uid 500); 7 Jan 2009 04:55:39 -0000 Delivered-To: apmail-hadoop-zookeeper-user-archive@hadoop.apache.org Received: (qmail 5277 invoked by uid 500); 7 Jan 2009 04:55:39 -0000 Mailing-List: contact zookeeper-user-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: zookeeper-user@hadoop.apache.org Delivered-To: mailing list zookeeper-user@hadoop.apache.org Received: (qmail 5266 invoked by uid 99); 7 Jan 2009 04:55:39 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 06 Jan 2009 20:55:39 -0800 X-ASF-Spam-Status: No, hits=2.2 required=10.0 tests=HTML_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of burtonator@gmail.com designates 72.14.246.241 as permitted sender) Received: from [72.14.246.241] (HELO ag-out-0708.google.com) (72.14.246.241) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 07 Jan 2009 04:55:30 +0000 Received: by ag-out-0708.google.com with SMTP id 9so6058141agd.9 for ; Tue, 06 Jan 2009 20:55:09 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:sender :to:subject:in-reply-to:mime-version:content-type:references :x-google-sender-auth; bh=eQAN783/JvoABoIONPEv2pkTasgP7LfLvPQh1yRfGgU=; b=c1GNcsCDRdWbGLqwLbKPc7xigHIYO3cXwTWoBOP/YuyZokY1IaIGXmAiOLrcX5m1lp /doaV51v156hJ8v0pIIqdr0L5SpuBkmqfqJnQKl9RvDv7Y7fYiOnoG1pt4g40p0QXSBR QEgrj/3tq1N0w3ie38S4VY6E1pzYEC0HOfLpc= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:sender:to:subject:in-reply-to:mime-version :content-type:references:x-google-sender-auth; b=jaPmvN4QEplBgv51eOiZARl60tYyTgJl829svUC7F0fK5A5j/XTjxrFc8ColfZZe+w U144XjzSBLF+UUhss2Fup1nYBSByPNnT/fdjtvw94XcW9FnPEkBp/KVyTBLXJ0nbIHoC 1BoyIfu+I6ZLAVlvI3FkFF4hGWgcreUEYXKZI= Received: by 10.90.30.2 with SMTP id d2mr10634992agd.58.1231304109726; Tue, 06 Jan 2009 20:55:09 -0800 (PST) Received: by 10.90.98.6 with HTTP; Tue, 6 Jan 2009 20:55:09 -0800 (PST) Message-ID: <30c6373b0901062055m7cc3c64bjd7d4c48897cabf9b@mail.gmail.com> Date: Tue, 6 Jan 2009 20:55:09 -0800 From: "Kevin Burton" Sender: burtonator@gmail.com To: zookeeper-user@hadoop.apache.org Subject: Re: Sending data during NodeDataChanged or NodeCreated In-Reply-To: MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_4773_19003953.1231304109716" References: <30c6373b0901061639s700430edj5e879e62e19adec5@mail.gmail.com> X-Google-Sender-Auth: f99ab379102ee2d1 X-Virus-Checked: Checked by ClamAV on apache.org ------=_Part_4773_19003953.1231304109716 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline > > > It's almost certainly what the user wants anyway. > Its just that the watches are pretty lightweight and sending bytes around > is > just more work to do at the server. Though we should experiment with how > much more load it generates and how useful would it be to send out the > bytes > with the event of nodedatachanged and nodecreated. > It might just be an alternate method... maybe not returning the data by default. It would solve the issue of deletes after NodeDataChange .... Kevin -- Founder/CEO Spinn3r.com Location: San Francisco, CA AIM/YIM: sfburtonator Skype: burtonator Work: http://spinn3r.com ------=_Part_4773_19003953.1231304109716--