Micah,

I assume you've looked at FeedSync and determined it doesn't meet you
needs? Can you explain why?

http://dev.live.com/feedsync/spec/spec.aspx


On Wed, Apr 7, 2010 at 9:57 AM, Micah <[email protected]> wrote:
> Hi,
>
> I'm building (yet another) RSS/Atom syndication/syncing service, and
> I'm thinking of basing it on PuSH. My goal is to track external (ie.
> not under my control) RSS/Atom feeds and syndicate them to another
> location. Or, put simpler, I want to replicate an RSS/Atom feed in
> another location.
>
> I started out doing this with Superfeedr, but I ran into a major issue
> with updates. I need the feeds to stay in sync, so if the original
> feed is updated, I need those changes reflected in the syndicated
> display. Superfeedr (afaik) only sends notifications for new posts,
> not updates to existing posts. What about the reference implementation
> running on App Engine? How does it handle updates?
>
> Plus, since I don't control the external feeds, I'd like to use a hub
> that supports polling of feeds that aren't PuSH enabled. It's either
> that or I write my own poller.
>
> So, a summary:
>
> 1) I don't have control of the feeds, and many of them will not be
> PuSH enabled. Those that are not enabled will need to be polled.
> 2) I need to receive updates to the feeds, not just new posts. I'd be
> fine receiving the entire Atom feed every time, as long as someone
> else is doing the polling and just POSTing the entire thing to me.
> 3) I don't want to write my own polling service, as that's the real
> heavy lifting here, and if I do that, there's really no place for PuSH
> in my app.
> 4) I can run my own hub, if that would help, but I'd prefer to
> configure one out of the box, as opposed to hacking in the features I
> need.
>
> Any recommendations? Am I fundamentally misunderstanding PuSH and what
> it's used for?
>
> P.S. Sorry if this is a double-post. I tried posting before and it
> never showed up.
>
>
> --
> To unsubscribe, reply using "remove me" as the subject.
>



-- 
darren bounds
[email protected]

Reply via email to