Return-Path: Delivered-To: apmail-incubator-esme-dev-archive@minotaur.apache.org Received: (qmail 5026 invoked from network); 5 Sep 2010 09:42:05 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 5 Sep 2010 09:42:05 -0000 Received: (qmail 58718 invoked by uid 500); 5 Sep 2010 09:42:04 -0000 Delivered-To: apmail-incubator-esme-dev-archive@incubator.apache.org Received: (qmail 58655 invoked by uid 500); 5 Sep 2010 09:42:02 -0000 Mailing-List: contact esme-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: esme-dev@incubator.apache.org Delivered-To: mailing list esme-dev@incubator.apache.org Received: (qmail 58641 invoked by uid 99); 5 Sep 2010 09:42:01 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 05 Sep 2010 09:42:01 +0000 X-ASF-Spam-Status: No, hits=0.3 required=10.0 tests=FREEMAIL_FROM,RCVD_IN_DNSWL_NONE,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL,URIBL_RHS_DOB X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of esjewett@gmail.com designates 74.125.82.43 as permitted sender) Received: from [74.125.82.43] (HELO mail-ww0-f43.google.com) (74.125.82.43) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 05 Sep 2010 09:41:56 +0000 Received: by wwi14 with SMTP id 14so2698249wwi.0 for ; Sun, 05 Sep 2010 02:41:35 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:content-type; bh=Mme72IRyR+4DL6mt3YuEJUhbV9tex7SfXspe5UjQ+94=; b=iowu7I0HxrMn7txgC6a9kpU2Y54CwRLckdrosxTCNB7j1p63Odv74TUUIuZE+OUABX xMBWxrxO5U/c5z1j5rmidDpVZzgrL8ZULZJm7uJKgbGsRkefeZwkQph9uPNmi7EyVk2v CosoruHNHWr62RfWUIjzEgGdUYVAPXzWZoDvs= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=NpSErw1fBI7jBkZX2tnf7PXjOxxI3nlxSH46ZTr6piV8pJTpYc8JgMGtKawqhvCp21 zfPjEljUXNo3QSYgFXGr9WAF3W6Hq+XmxZ1RNxSgYSFvrqQC6XZh7uK4ziWuJDVzpW9f jw3QlmOklVzM5CnbhwCdK4ZF10cfZqUmFOwYE= MIME-Version: 1.0 Received: by 10.227.132.199 with SMTP id c7mr988351wbt.89.1283679695229; Sun, 05 Sep 2010 02:41:35 -0700 (PDT) Received: by 10.227.199.81 with HTTP; Sun, 5 Sep 2010 02:41:35 -0700 (PDT) In-Reply-To: <654FD11ACA004B81B9530A9DD6DBF33C@imtiaz20100131> References: <18D2DB57E5FD43B0A44F299209166660@imtiaz20100131> <654FD11ACA004B81B9530A9DD6DBF33C@imtiaz20100131> Date: Sun, 5 Sep 2010 11:41:35 +0200 Message-ID: Subject: Re: Is doing PubSubHubub worth it ? From: Ethan Jewett To: esme-dev@incubator.apache.org Content-Type: text/plain; charset=ISO-8859-1 Hmmm, you're right, it looks like a Jira item doesn't exist for that. Ok, I've created two Jira tickets in the backlog: ESME-271 - Provide authenticated Atom/RSS feeds of timelines - https://issues.apache.org/jira/browse/ESME-271 ESME-272 - Pubsubhubbub-enable timeline feeds - https://issues.apache.org/jira/browse/ESME-272 I'm not sure if that's enough information, or even if they contain the right design decisions. Let's discuss further on the list or in the comments of the Jira issues. Ethan On Sun, Sep 5, 2010 at 7:37 AM, Imtiaz Ahmed H E wrote: > Ethan, > > Could you create the Jira item for authenticated RSS feeds with suifficient > detail and let us know when you are done. I'm curious... > > Imtiaz > > ----- Original Message ----- From: "Ethan Jewett" > To: > Sent: Saturday, September 04, 2010 4:23 PM > Subject: Re: Is doing PubSubHubub worth it ? > > >> I think we just need the authenticated RSS feeds first. Another issue >> dependent on the RSS feed issue would make sense. I'll try to remember >> to do it when I get home. >> >> Agreed on it being in the Backlog, not 1.2. >> >> Ethan >> >> On Saturday, September 4, 2010, Richard Hirsch >> wrote: >>> >>> Do we want to create another JIRA issue for Pubsubhubbub publishing? >>> Don't know whether it would be 1.2 though: >>> >>> D. >>> >>> On Sat, Sep 4, 2010 at 10:49 AM, Imtiaz Ahmed H E >>> wrote: >>>> >>>> I think I'll just go ahead and do it and the rest of you can review my >>>> completed stuff and it's working in the svn pubsubhubub-2 branch and >>>> decide >>>> whether to go ahead and integrate with trunk or not. >>>> >>>> I'll try to deliver quickly now! >>>> >>>> Imtiaz >>>> >>>> ----- Original Message ----- From: "Ethan Jewett" >>>> To: >>>> Sent: Saturday, September 04, 2010 1:40 PM >>>> Subject: Re: Is doing PubSubHubub worth it ? >>>> >>>> >>>>> It's a good question - perfectly reasonable. As Dick mentioned, I >>>>> don't think that list is complete, but it's true that not everybody >>>>> has implemented PuSH. >>>>> >>>>> In my mind, Pubsubhubbub is a nice-to-have at this point. It's >>>>> definitely not one of the highest priority items. It's something that >>>>> I was interested in implementing as an experiment and it would >>>>> immediately deliver some additional nice functionality in the form of >>>>> instantly updating actions and less server time spent downloading RSS >>>>> feeds every X minutes. >>>>> >>>>> Longer-term, there are more interesting implications if we get >>>>> PuSH-enabled, authenticated feeds of ESME user timelines (with ESME as >>>>> a publisher and hub). Once this happens, it is another good way to >>>>> integrate ESME with other systems on a user-by-user basis. Eventually >>>>> it might be a way to federate ESME instances, but there are a lot of >>>>> complications that are not easily resolved, including what is done >>>>> about pools in this scenario and how authentication works (PuSH >>>>> authentication is not a very well-resolved problem). >>>>> >>>>> So, that's just my partially-formed thinking on the topic. It was >>>>> pretty much a science-project for me that didn't get very far. I >>>>> definitely think of it as a nice-to-have rather than a "must-have". >>>>> >>>>> Ethan >>>>> >>>>> On Sat, Sep 4, 2010 at 9:58 AM, Richard Hirsch >>>>> wrote: >>>>>> >>>>>> There are some other companies not on the list but present in the >>>>>> comments (RabbitMQ and status.net) - there are also some interesting >>>>>> other possibilities (for example, linking it to xmpp ( >>>>>> http://grack.com/blog/2009/09/09/pubsubhubbub-to-xmpp-gateway/) or >>>>>> this blog about pubsubhubbub and twitter >>>>>> (http://blog.persistent.info/2009/08/twitter-pubsubhubbub-bridge.html) >>>>>> Since we've already started the implementation, I'd really be >>>>>> interested in continuing it but I'm open for discussions on the topic >>>>>> as well. >>>>>> >>>>>> D. >>>>>> >>>>>> On Sat, Sep 4, 2010 at 9:11 AM, Imtiaz Ahmed H E >>>>>> wrote: >>>>>>> >>>>>>> Please don't misconstrue me, I would have (and already started >>>>>>> having) >>>>>>> my usual ball doing it! >>>>>>> >>>>>>> But at http://code.google.com/p/pubsubhubbub/wiki/Companies >>>>>>> there are only a handful of companies who have advertised themselves >>>>>>> as >>>>>>> doing (supporting a hub for their feeds) it. >>>>>>> >>>>>>> Of course, Ethan probably knows better... >>>>>>> >>>>>>> What do you think ? Dick ? >>>>>>> >>>>>>> Maybe there's lots of other stuff that would really help Esme. But, >>>>>>> pubsubhubub is a really worthwhile api/concept in itself... >>>>>>> >>>>>>> Imtiaz >>>>>>> >>>>>>> >>>>>> >>>> >>>> >>> > >