stompserver 0.9.3 → 0.9.4
Sign up to get free protection for your applications and to get access to all the features.
- data/History.txt +13 -0
- data/README.txt +2 -1
- data/bin/stompserver +18 -3
- data/lib/frame_journal.rb +1 -0
- data/lib/stomp_server.rb +2 -1
- data/test/test_topic_manager.rb +1 -1
- metadata +3 -3
data/History.txt
CHANGED
@@ -1,3 +1,16 @@
|
|
1
|
+
== 0.9.4 / 17 Oct 2006
|
2
|
+
|
3
|
+
* Cleanup (wow I was tired last night)
|
4
|
+
* Tested under Linux, added require 'rubygems'
|
5
|
+
* Fixed stompserver binary - it now works and takes a few simple command args
|
6
|
+
* Fixed up minor (tesly) test syntax issues
|
7
|
+
|
8
|
+
== 0.9.3 / 16 Oct 2006
|
9
|
+
|
10
|
+
* Last one tonight I promise
|
11
|
+
* Fixed incorrect gem requirement version on eventmachine
|
12
|
+
* Fixed stompserver cmd added by gem
|
13
|
+
|
1
14
|
== 0.9.2 / 16 Oct 2006
|
2
15
|
|
3
16
|
* More Queue issues resolved
|
data/README.txt
CHANGED
@@ -16,7 +16,6 @@ Does not support any server to server messaging
|
|
16
16
|
(although you could write a client to do this)
|
17
17
|
Server Id is not being well initialized
|
18
18
|
Quite a bit of polish is still required to make into a daemon/service
|
19
|
-
and add command line handling.
|
20
19
|
And oh yeah, I need to write some docs (see the tests for now)
|
21
20
|
|
22
21
|
== SYNOPSYS:
|
@@ -31,6 +30,8 @@ Handles basic message queue processing
|
|
31
30
|
== INSTALL:
|
32
31
|
|
33
32
|
+ Grab the gem
|
33
|
+
and run:
|
34
|
+
stompserver -p 61613 -b 0.0.0.0 -j /var/ss/journal_dir
|
34
35
|
|
35
36
|
== LICENSE:
|
36
37
|
|
data/bin/stompserver
CHANGED
@@ -1,7 +1,22 @@
|
|
1
1
|
require 'rubygems'
|
2
|
-
require '
|
2
|
+
require 'stomp_server'
|
3
|
+
require 'frame_journal'
|
4
|
+
require 'optparse'
|
3
5
|
|
4
|
-
|
6
|
+
opts = OptionParser.new
|
7
|
+
|
8
|
+
port = 61613
|
9
|
+
bind = "127.0.0.1"
|
10
|
+
journal = ".stompserver"
|
11
|
+
|
12
|
+
opts.on("-p", "--port=PORT", Integer) {|p| port = p}
|
13
|
+
opts.on("-b", "--bind=ADDR", String) {|a| bind = a}
|
14
|
+
opts.on("-j", "--journal=DIR", String) {|j| journal = j}
|
15
|
+
|
16
|
+
puts opts.parse(ARGV)
|
17
|
+
|
18
|
+
StompServer.setup(FrameJournal.new(journal))
|
5
19
|
EventMachine::run do
|
6
|
-
|
20
|
+
puts "Stomp Server starting on port #{port}"
|
21
|
+
EventMachine.start_server bind, port, StompServer
|
7
22
|
end
|
data/lib/frame_journal.rb
CHANGED
data/lib/stomp_server.rb
CHANGED
@@ -1,3 +1,4 @@
|
|
1
|
+
require 'rubygems'
|
1
2
|
require 'eventmachine'
|
2
3
|
require 'stomp_frame'
|
3
4
|
require 'topic_manager'
|
@@ -5,7 +6,7 @@ require 'queue_manager'
|
|
5
6
|
require 'frame_journal'
|
6
7
|
|
7
8
|
module StompServer
|
8
|
-
VERSION = '0.9.
|
9
|
+
VERSION = '0.9.4'
|
9
10
|
VALID_COMMANDS = [:connect, :send, :subscribe, :unsubscribe, :begin, :commit, :abort, :ack, :disconnect]
|
10
11
|
|
11
12
|
def self.setup(j = FrameJournal.new, tm = TopicManager.new, qm = QueueManager.new(j))
|
data/test/test_topic_manager.rb
CHANGED
metadata
CHANGED
@@ -3,8 +3,8 @@ rubygems_version: 0.9.0
|
|
3
3
|
specification_version: 1
|
4
4
|
name: stompserver
|
5
5
|
version: !ruby/object:Gem::Version
|
6
|
-
version: 0.9.
|
7
|
-
date: 2006-10-
|
6
|
+
version: 0.9.4
|
7
|
+
date: 2006-10-17 00:00:00 -04:00
|
8
8
|
summary: A very light messaging server
|
9
9
|
require_paths:
|
10
10
|
- lib
|
@@ -12,7 +12,7 @@ require_paths:
|
|
12
12
|
email: phurley@gmail.com
|
13
13
|
homepage: " by Patrick Hurley"
|
14
14
|
rubyforge_project: stompserver
|
15
|
-
description: "Don't want to install a JVM, but still want to use messaging? Me too, so I threw together this little server. All the hard work was done by Francis Cianfrocca (big thank you) in his event machine gem (which is required by this server). == FEATURES/PROBLEMS: Handles basic message queue processing Does not support any server to server messaging (although you could write a client to do this) Server Id is not being well initialized Quite a bit of polish is still required to make into a daemon/service
|
15
|
+
description: "Don't want to install a JVM, but still want to use messaging? Me too, so I threw together this little server. All the hard work was done by Francis Cianfrocca (big thank you) in his event machine gem (which is required by this server). == FEATURES/PROBLEMS: Handles basic message queue processing Does not support any server to server messaging (although you could write a client to do this) Server Id is not being well initialized Quite a bit of polish is still required to make into a daemon/service And oh yeah, I need to write some docs (see the tests for now)"
|
16
16
|
autorequire:
|
17
17
|
default_executable:
|
18
18
|
bindir: bin
|