PUSHEE

From IIW
Revision as of 21:14, 5 May 2011 by Ebgross (talk | contribs)

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search

Session Topic: PuSHee talk with Mitre team (T3F)

Convener: Justin Richer

Notes-taker(s): Monica Wilkinson


Tags for the session - technology discussed/ideas considered:


Discussion notes, key understandings, outstanding questions, observations, and, if appropriate to this discussion: action items, next steps:


Requirements: Providing calls to action for users in the enterprise based on a variety of business data sources

Methodology:  PubSubHubbub and Activity Streams using OAuth 2.0

Url: http://code.google.com/p/pushee... Java Spring

Not everyone likes Java in the room but Jason mentions that is a solid enterprise framework and they have added unit testing and monitoring components

Jason described PubSubHubbub highlighting the PubSub aspects

PuShee = Pubsubhubbub Hub with oAuth 2.0 for Pub and Sub

PUSHee Includes an authorization server with UI to manage keys/secrets

Subscription rules are managed via UI instead of independently for each resource


Use case: PubSub for Medical. Justin asks to checkout the hdata project

Use case is one generic notification engine which is surfaced on intranet

Audience asked: What happens to late subscribers ?

One idea publishing to a topic and then have the topic support or not support late subscribers

Justin mentions that he wants any publisher and client to be able to use PuSHee

Clients needs to know url of resource, have a POST end point and support verification of the request via oAuth or JWT.

One of the principles TOFU = Trust On First Use

Open Source Project anyone can join includes aggregator

Clients need to have a web server

What about having multiple subscribers asks the audience

The client in PuSHee is really the Activity Stream engine that users would subscribe to

San Jose-20110503-00054.jpg