search

progrium / http-subscriptions

54 stars 1 forks source link

Difference from PuSH ? #3

Open vasilakisfil opened 9 years ago

vasilakisfil commented 9 years ago

What http-subscriptions try to achieve? A pub-sub protocol without hubs ?

progrium commented 9 years ago

No hub, no coupling of publish semantics. No assumptions about payloads. Simpler. Lots of things.

On Mon, Jan 5, 2015 at 3:21 PM, Filippos Vasilakis <notifications@github.com

wrote:

What http-subscriptions try to achieve? A pub-sub protocol without hubs ?

— Reply to this email directly or view it on GitHub https://github.com/progrium/http-subscriptions/issues/3.

Jeff Lindsay http://progrium.com

vasilakisfil commented 9 years ago

ok! Personally I would do leasing and subscription refreshing using oauth2 authorization flow (or even implicit flow) and using JWT tokens. Something like: pub-sub--oauth2-full

of course publisher/IdP could be in the same box, so as user/subscriber.

progrium commented 9 years ago

Very interesting idea! Thanks for the graphic ... I'll use it when I revisit HTTP subscriptions.

On Thu, Jan 15, 2015 at 10:42 AM, Filippos Vasilakis < notifications@github.com> wrote:

ok! Personally I would do leasing and subscription refreshing using oauth2 authorization flow (or even implicit flow) and using JWT tokens. Something like: [image: pub-sub--oauth2-full] https://cloud.githubusercontent.com/assets/590575/5761734/a059d480-9cdd-11e4-890a-802cef2231e9.png

— Reply to this email directly or view it on GitHub https://github.com/progrium/http-subscriptions/issues/3#issuecomment-70115967 .

Jeff Lindsay http://progrium.com