Thanks for the 100th episode - can't believe you did 100 already.
The Windows Azure Service Bus Notification Hub feature looks really interesting, but following the walkthrough of the APIs, I can't help but wonder about the naming of the API operators. What's up with the extremely long method names? I know you're reaching for a broad developer base here but there's really no reason to materialize all combinations of permissions as concrete methods.
I'm sure the developers of the WASBNH APIs are capable of shorter names / more elegant namings than the following (combined with a set of enums, and associated overloads).
It feels like the API was designed to be used with simple one-liners, perhaps leaving the impression of simplicity but at the cost of elegance, and future evolution of the APIs. Am I the only one asking for more consistent API designs in the Windows Azure APIs in general?!