Like Brad said, this is in religious war territory. People often conclude,
"the base spec should just support X, and the rest is optional." But then X
is async if you talk to Pádraic and sync if you talk to Julien. It does make
things worse for hubs, but the complexity should be pushed there to handle
this to make subscribers' lives easier.

However, keep in mind that all subscribers need some sort of async support
anyways since automatic subscription refreshing is an async process. So it's
almost like the base spec does require both sync and async verification,
depending on what's easiest in your framework?

So I'd advocate a third option here: Requiring all Hubs to implement both
sync and async (sorry Julien ;P). Thoughts?

-Brett

On Sun, Oct 18, 2009 at 5:51 PM, Jay Rossiter <[email protected]> wrote:

>
>     I do have to agree with others in that the complexity isn't isolated to
> the hub.  Since it's clear that various hubs are implementing either sync or
> async (but rarely both, from the conversations here), it means that the
> subscriber is *required* to support both, if it wants interoperability
> with all hubs.
>
>     I think that at the hub, both sync and async should be mandatory, and
> the subscribers should be able to do whatever is easiest for them.
>
>
> On 10/18/2009 2:11 PM, Brad Fitzpatrick wrote:
>
> We debated this for a long time.  There are groups of people adamant about
> both ways.  :-/
>  In keeping with the overall design goal of keeping pub+sub simple and
> pushing complexity to the hub, we chose to push complexity to the hub here.
>
> On Sat, Oct 17, 2009 at 9:45 PM, Tim Bray <[email protected]> wrote:
>
>>
>> I read this one and I'm thinking YAGNI.  It seems like the flexibility
>> here adds complexity and doesn't really buy that much.  Why not just
>> settle on async and leave it at that?
>>
>>  -T
>>
>
>
>
> --
>
> Jay Rossiter | Software Engineer/System Administrator
> Pioneering RSS Advertising Solutions
>
> [email protected] | Phone: 503.896.6187 | Fax: 503.235.2216
> Website: www.pheedo.com | RSS: www.pheedo.info/index.xml
>

<<pheedo.gif>>

Reply via email to