Well, depends on the workaround I suppose ;). The Zend client does allow for callback ID encoding within the callback URIs path. It's an opt-in "workaround" of sorts for Hubs not complying with later versions of the specification. It's problem, of sorts, is that the opt-in requires additional changes to application routing. Easy for me to say that since it was added months ago, we have examples, and kept it simple - but doing it in a current application can be a chore. If you take something like Drupal or even Wordpress into account you have even worse problems - both are widely deployed in scenarios where doing things like adding workarounds and mod_rewrite rules isn't something the user can do and probably isn't something a developer is likely to commit to given the outdatedness of 0.1. Not saying that's the case, but it does edge Typepad out into the category of implementors who are shooting themselves in the foot by using an outdated specification new libraries would prefer not to accommodate.
Here's to the timeline being...soon :). Pádraic Brady http://blog.astrumfutura.com http://www.survivethedeepend.com OpenID Europe Foundation Irish Representative ________________________________ From: vivpuri <[email protected]> To: Pubsubhubbub <[email protected]> Sent: Wed, March 17, 2010 12:55:55 AM Subject: [pubsubhubbub] Re: PubSubHubbub sub issue on Typepad Not sure about Waleed, personally i try to stay away from workarounds. 'cause then you have workarounds for workarounds, and the loop continues. And after few days workarounds collide, you look at the code and are thinking, who wrote this pathetic code. In my case, i code alone, so no one else to blame either :(
