stompserver 0.9.3 → 0.9.4

data/History.txt

@@ -1,3 +1,16 @@
+== 0.9.4 / 17 Oct 2006
+
+* Cleanup (wow I was tired last night)
+  * Tested under Linux, added require 'rubygems' 
+  * Fixed stompserver binary - it now works and takes a few simple command args
+  * Fixed up minor (tesly) test syntax issues
+
+== 0.9.3 / 16 Oct 2006
+
+* Last one tonight I promise
+  * Fixed incorrect gem requirement version on eventmachine
+  * Fixed stompserver cmd added by gem
+
 == 0.9.2 / 16 Oct 2006
 
 * More Queue issues resolved

data/README.txt

@@ -16,7 +16,6 @@ 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 add command line handling.
 And oh yeah, I need to write some docs (see the tests for now)
 
 == SYNOPSYS:
@@ -31,6 +30,8 @@ Handles basic message queue processing
 == INSTALL:
 
 + Grab the gem
+  and run:
+    stompserver -p 61613 -b 0.0.0.0 -j /var/ss/journal_dir
 
 == LICENSE:
 

data/bin/stompserver

@@ -1,7 +1,22 @@
 require 'rubygems'
-require 'stompserver'
+require 'stomp_server'
+require 'frame_journal'
+require 'optparse'
 
-StompServer.setup
+opts = OptionParser.new
+
+port = 61613
+bind = "127.0.0.1"
+journal = ".stompserver"
+
+opts.on("-p", "--port=PORT", Integer)   {|p| port = p}
+opts.on("-b", "--bind=ADDR", String)    {|a| bind = a}
+opts.on("-j", "--journal=DIR", String)  {|j| journal = j}
+
+puts opts.parse(ARGV)
+ 
+StompServer.setup(FrameJournal.new(journal))
 EventMachine::run do
-  EventMachine.start_server "0.0.0.0", 61613, StompServer
+  puts "Stomp Server starting on port #{port}"
+  EventMachine.start_server bind, port, StompServer
 end

data/lib/frame_journal.rb

@@ -10,6 +10,7 @@
 #
 # When the size of a journal file exceeds its limit
 
+require 'rubygems'
 require 'madeleine'
 require 'madeleine/automatic'
 

data/lib/stomp_server.rb

@@ -1,3 +1,4 @@
+require 'rubygems'
 require 'eventmachine'
 require 'stomp_frame'
 require 'topic_manager'
@@ -5,7 +6,7 @@ require 'queue_manager'
 require 'frame_journal'
 
 module StompServer
-  VERSION = '0.9.3'
+  VERSION = '0.9.4'
   VALID_COMMANDS = [:connect, :send, :subscribe, :unsubscribe, :begin, :commit, :abort, :ack, :disconnect]
 
   def self.setup(j = FrameJournal.new, tm = TopicManager.new, qm = QueueManager.new(j))

data/test/test_topic_manager.rb

@@ -1,6 +1,6 @@
 require 'topic_manager'
 require 'test/unit' unless defined? $ZENTEST and $ZENTEST
-require 'tesly_reporter'
+require 'tesly'
 
 class TestTopics < Test::Unit::TestCase
 

metadata

@@ -3,8 +3,8 @@ rubygems_version: 0.9.0
 specification_version: 1
 name: stompserver
 version: !ruby/object:Gem::Version 
-  version: 0.9.3
-date: 2006-10-16 00:00:00 -04:00
+  version: 0.9.4
+date: 2006-10-17 00:00:00 -04:00
 summary: A very light messaging server
 require_paths: 
 - lib
@@ -12,7 +12,7 @@ require_paths:
 email: phurley@gmail.com
 homepage: "    by Patrick Hurley"
 rubyforge_project: stompserver
-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 add command line handling. And oh yeah, I need to write some docs (see the tests for now)"
+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)"
 autorequire: 
 default_executable: 
 bindir: bin