Compliance for Superfeedr's Hubs

Compliance for Superfeedr's Hubs

We said it in the past, abiding by standards makes the web better. Yet, sometimes, standards have a tendency to diverge from an implementation to another. You know, the theory vs. practice thing.

PubSubHubbub is a standard. Since it’s relies on HTTP, it makes it quite easy to test and specify, and that’s what progrium did a while ago.

Today I checked and cleaned a little bit the test suite, and I uploaded it to Superfeedr’s github repo. I tested it with the hubs we host and, good news : we’re fully compliant on the subscriber part :)

The publisher part is a little bit trickier, because it expects the hub to fetch a url after a ping. However, in Superfeedr’s case, the scheduling algorithm is a slightly more complex, and it makes it “non-deterministic” from the outside world : quite hard to specify.

Obviously, you can run that code by yourself to make sure we’re doing good! We will also try to update both the hub and the test suite when the specification evolves! (Also, I need to find a way to push that back to Google’s svn, but my svn is probably not better than my ancient greek…)

Liked this post? Read the archive or

Previously, on the Superfeedr blog: Who Implemented PubSubHubbub.