Return-Path: Delivered-To: apmail-jackrabbit-users-archive@locus.apache.org Received: (qmail 56352 invoked from network); 17 May 2007 19:29:48 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 17 May 2007 19:29:48 -0000 Received: (qmail 16514 invoked by uid 500); 17 May 2007 19:29:54 -0000 Delivered-To: apmail-jackrabbit-users-archive@jackrabbit.apache.org Received: (qmail 16332 invoked by uid 500); 17 May 2007 19:29:53 -0000 Mailing-List: contact users-help@jackrabbit.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: users@jackrabbit.apache.org Delivered-To: mailing list users@jackrabbit.apache.org Received: (qmail 16322 invoked by uid 99); 17 May 2007 19:29:53 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 17 May 2007 12:29:53 -0700 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (herse.apache.org: domain of stefan.kurla@gmail.com designates 64.233.166.181 as permitted sender) Received: from [64.233.166.181] (HELO py-out-1112.google.com) (64.233.166.181) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 17 May 2007 12:29:46 -0700 Received: by py-out-1112.google.com with SMTP id h31so1529966pyc for ; Thu, 17 May 2007 12:29:25 -0700 (PDT) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=nzna/gVpCJt+ugHLTRiYQv9SAl+1RXju46VGdTOvo5A7Rq2qFVzsX8LICvYaqokZ2okF/XBoXfPE9py4glXSorwoMrkt4wfMGCaM2S+Z0/weu8klWPf/VzDXV17fkL/Ghz6bKJxUwK2pOIZ+OEESnH04MXyZ6TQpY7cFvvo0twY= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=G8H9XRYO+g/1/OOWjmcPhT9h8R/UDfw5fySFF+F/0NjkWsk+GAkJ2JvDJJ3RZmSMhDuXvKcKUiC8BBJB2sBe+gAhmRUEME5LTFQl+4CVbHoMfLkpgwqIynK6E4upS6KXn3p/cai2HtkB3VH9HyuXlRDHEQwZZDOz8lV/p+Ve85g= Received: by 10.65.43.17 with SMTP id v17mr4804772qbj.1179430165125; Thu, 17 May 2007 12:29:25 -0700 (PDT) Received: by 10.65.83.2 with HTTP; Thu, 17 May 2007 12:29:24 -0700 (PDT) Message-ID: <86d42bef0705171229t62752de2nb295f1acc407ff4c@mail.gmail.com> Date: Thu, 17 May 2007 14:29:25 -0500 From: "Stefan Kurla" To: users@jackrabbit.apache.org Subject: Re: Question on creating RSS feeds In-Reply-To: <1179387200.6049.2.camel@antares> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <86d42bef0705161334icad0d91k6b259c4aa52c721d@mail.gmail.com> <1179387200.6049.2.camel@antares> X-Virus-Checked: Checked by ClamAV on apache.org > > > When building the feed support for InfoQ, I was thinking in terms of > > pull vs push feeds. I am not sure if these terms are usually used in > > conjunction with feeds, but what I mean is: is it possible to > > pregenerate my feed so that once I get a request this is already > > prepared (push model) or should I generate the feed each time I am > > receiving a request (pull model). Having these questions answered, > > I've been able to further implement things. AP=> What model did you choose? > > I'm planning also this feature for our application. Actually I have not > decided how to implement it, but I think the RSS will be generated on > each request because not all users have access to all the documents (Out > application is an document manager). That is the problem that i am facing as well. my feeds are going to be very personalized, one could be looking for events at /jcr:root/myFolder for changes the other could look at /jcr:root/myFolder2 for changes. If this were the case then I would have 2 event listeners then.. for 1000 such cases, there would 1000 event listeners. This would be the push model, where as the data is published the RSS xml is created or an email is sent out as a notification. That seems to be the model that i am looking for since we have to inform the user of the changes in the repository. Any suggestions?