explainer-rmb-rails 0.1.3 → 0.1.4
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- data/README.rdoc +6 -6
- data/VERSION +1 -1
- data/rmb-rails.gemspec +1 -1
- metadata +1 -1
data/README.rdoc
CHANGED
@@ -1,7 +1,7 @@
|
|
1
1
|
|
2
2
|
= rmb-rails: RESTful Message Beans for Ruby on Rails
|
3
3
|
|
4
|
-
|
4
|
+
== Introduction
|
5
5
|
|
6
6
|
During a lengthy career in software development, and later as an enterprise architect, I saw a lot of message broker deployments in many
|
7
7
|
large corporations. These systems were used primarily to knit together disparate computing 'silos' into a single fabric, as primarily
|
@@ -21,7 +21,7 @@ There is a real parallel between a Java EJB application and a Ruby-on-Rails appl
|
|
21
21
|
get incoming message broker subscriptions injected directly into the main Rails data stream. So, how can we convert an MQ message
|
22
22
|
into an http request? The rubygem rmb-rails addresses this issue.
|
23
23
|
|
24
|
-
|
24
|
+
== Theory of Operation
|
25
25
|
|
26
26
|
As stated above, experience shows that polling a queue to pick up messages waiting there does not scale well. I decided to create an
|
27
27
|
infrastructure where daemon processes, called listeners, can connect to a specified message broker, receive messages from that broker,
|
@@ -29,7 +29,7 @@ and then forward them on to a standard Rails controller using a standard Rails p
|
|
29
29
|
act as browsers doing a form of file upload. The receiving rails controller is built on standard REST principles, and fits easily into
|
30
30
|
any Rails application.
|
31
31
|
|
32
|
-
|
32
|
+
== Component classes
|
33
33
|
|
34
34
|
* module RMB
|
35
35
|
The rmb-rails gem is packaged within a single module, called RMB. The component classes are described below. See the rdoc for each class for a full description.
|
@@ -50,7 +50,7 @@ This is a concrete subclass of Subscriber, which uses the Stomp protocol to list
|
|
50
50
|
* class RMB::MechanizeSubmitter
|
51
51
|
This is a concrete subclass of Submitter, which uses the WWW:Mechanize gem to package the message as a document and submit it to the controller.
|
52
52
|
|
53
|
-
|
53
|
+
== Installation
|
54
54
|
|
55
55
|
You will need an ActiveMQ message broker to use this gem. See http://activemq.apache.org/ for download and configuration instructions.
|
56
56
|
|
@@ -61,7 +61,7 @@ $ sudo gem install explainer-rmb-rails
|
|
61
61
|
|
62
62
|
$ sudo gem install rmb-rails (to get the same gem from rubyforge)
|
63
63
|
|
64
|
-
|
64
|
+
== Usage
|
65
65
|
|
66
66
|
Add the following require statement to your code to get access to this gem:
|
67
67
|
|
@@ -72,7 +72,7 @@ RESTful-Message-Beans(http://github.com/explainer/RESTful-Message-Beans/tree/mas
|
|
72
72
|
demo rails application using this gem.
|
73
73
|
|
74
74
|
== Credits
|
75
|
-
{ActiveMQ}[http://activemq.apache.org/] find the message broker here
|
75
|
+
{ActiveMQ}[http://activemq.apache.org/] You can find the ActiveMQ message broker here.
|
76
76
|
|
77
77
|
{Enterprise Recipes with Ruby and Rails}[http://www.pragprog.com/titles/msenr/enterprise-recipes-with-ruby-and-rails] A special thanks to Maik Schmidt for this useful book.
|
78
78
|
|
data/VERSION
CHANGED
@@ -1 +1 @@
|
|
1
|
-
0.1.
|
1
|
+
0.1.4
|
data/rmb-rails.gemspec
CHANGED