We haven't looked at RabbitHub, but I don't think that it actually fits
our use cases. We're not running AMQP on anything right now, so how
would a gateway to it help? Besides, we're not just looking for an
implementation of PuSH, we're looking for something that we can
integrate into our enterprise environment. Java is the best-supported
language in our IT infrastructure, and Spring is very well-accepted by
the IT management crowd. We're also looking for things like
administration consoles and support for authorization systems like OAuth
and OAuth2. And ultimately, we want to build something scalable,
testable, maintainable and deployable. We looked at pubsubhubbub-java,
but that doesn't even make use of a servlet container let alone a larger
framework with which we could build our local customizations. 

 -- Justin

On Wed, 2011-03-23 at 17:37 -0400, Alexis Richardson wrote:
> Have you tried RabbitHub?
> 
> On Wed, Mar 23, 2011 at 7:46 PM, Justin Richer <[email protected]> wrote:
> > Hi all, allow me to introduce myself and our new project.
> >
> > I'm a researcher at the MITRE Corporation (www.mitre.org), and my team
> > is about to start up a new open source project to build an
> > enterprise-class engine for PubSubHubbub. We looked for something that
> > fit our needs and didn't see anything, so we're going to build one. Even
> > thought we're going to be building something that we can deploy and use
> > in our own IT environment, we thought that it was likely to be useful
> > enough to others out there that we would build the whole core as an open
> > source project that we're calling the PubSubHubbub Enterprise Engine --
> > or "PuSHEE".
> >
> > The main part of this will be a hub built on top of Spring3.0, and a
> > management console on top of that hub to control publishers,
> > subscribers, users, and other admin functionality that you would expect
> > from a deployable enterprise system. We'll also be building test
> > harnesses, client and publisher libraries, OAuth2 authorization systems,
> > and other support structures like that. In addition, we might be in a
> > good position to propose and work with extensions to the PuSH protocol
> > to handle things like publisher management or other issues that come
> > up.
> >
> > I'm writing to this community to invite any interested parties in
> > joining and following the project as we get it off the ground in the
> > next couple weeks. We welcome feedback, guidance, advice, and (of
> > course) working code contributions. You can see the empty shell of our
> > project up on GoogleCode here:
> >
> >  http://code.google.com/p/pushee/
> >
> > It's just an empty spring shell right now, but I promise it'll get much
> > more interesting shortly. I look forward to working with you all on
> > this!
> >
> >  -- Justin Richer
> >    Senior Computer Scientist
> >    The MITRE Corporation
> >
> >


Reply via email to