Episode 100 - Introduction to the Windows Azure Service Bus Notification Hubs

Play Episode 100 - Introduction to the Windows Azure Service Bus Notification Hubs

The Discussion

  • User profile image
    Reperion

    Congratulations on the 100th episode !

    ..and thanks a bunch for WASBNH  Tongue Out

  • User profile image
    hornygoatwe​ed

    Not sure if I count as "several".

    When will pricing details be released?

  • User profile image
    Borum.NET

    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).

    • CreateUsingSharedSecret()
    • CreateUsingSharedAccessSecret()
    • CreateUsingSharedAccessSecretWithListenAccess()
    • CreateUsingSharedAccessSecretWithFullAccess()

    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?!

    Smiley

  • User profile image
    Elio Damaggio

    Hi Borum.NET,

    It is always hard to strike a balance between elegance and practicality for the common case.

    Regarding the specific example, the ConnectionString class was a particularly hard one as at the moment it is used in both mainstream and advanced scenarios.
    This is a point in time situation as in the (not so distant!) future the Portal will generate connections strings, this will make the above a very advanced scenario where we can support more elegant (albeit more complex) APIs.

    On a side note, the preview is also a time when we gladly welcome feedback of this kind on the APIs. We are already planning to improve the current APIs in many ways. So keep it coming!

  • User profile image
    Eliob Damaggio

    @hornygoatweed

    We are working hard to release pricing details soon.
    The current information I can share are on the pricing page of windowsazure.com: https://www.windowsazure.com/en-us/pricing/details/#header-7.

    "The price during General Availability will be based on the number of users (active registrations) receiving push notifications, and will be priced competitively to provide high-volume, multi-platform push notifications at a low monthly fee."

    Stay tuned for updates!

  • User profile image
    David_Lean

    Guy's,

    I Iove your program. Given how fast Azure is innovating, you save so much time in keeping us up to date & making us aware of what we can do. 

    While the jovial aspect is good, as are the little sound bites & graphics. I'd encourage you to stay on message & tighten up your intro. Most folks I know are very busy & charge a lot per hour. The 5-10 mins of personal junk at the start & they've turned you off before they get to the really worthwhile content.

    Thanks guys & happy 100th

    PS: Azure NH is a definite winner.

Conversation locked

This conversation has been locked by the site admins. No new comments can be made.