Mingle 3.3 introduced a new Events API in the form of an "Atom feed":http://www.thoughtworks-studios.com/mingle/3.3/help/mingle_api_events.html. The Mingle team and ThoughtWorks Studios are big believers in the use of Atom for exposing events. Atom is a widely used standard, and this event API style puts the issue of robust event delivery in the hands of the consumer, where it belongs. In fact, we'd argue this is the only feasible means of robust, scalable event delivery, short of spending hundreds of thousands or millions of dollars on enterprise buses and such. Atom-delivered events are cheap, scalable, standards-based, and robust. However, we do accept that asking integrators wishing to consume events to implement polling is not ideal. Writing polling consumers can be tedious. And this tedium gets in the way of writing sweet Mingle integrations. We are addressing this by publishing libraries such as this, which if effective, fully hide the mechanics of event polling from the consumer. The consumer only need worry about the processing of events. Said processing is modeled in the style of 'pipes and filters.'
Required Ruby Version
>= 0
Required Rubygems Version
>= 1.2
Authors
David Rice
Versions
-
0.2.3
-
source
- 0.2.3 source September 10, 2015 (35.5 KB)
-
-
0.2.1
-
source
- 0.2.1 source March 11, 2015 (35.5 KB)
-
-
0.2.0
-
source
- 0.2.0 source March 10, 2015 (35 KB)
-
-
0.1.9
-
source
- 0.1.9 source February 08, 2015 (35 KB)
-
-
0.1.8
-
source
- 0.1.8 source February 08, 2015 (35 KB)
-