iprocess 5.0.5 → 5.1.0

data/README.md

@@ -54,27 +54,17 @@ __3.__
 
 A demo of how you would spawn two subprocesses asynchronously.
 Although the subprocesses are spawned asynchrounsly you can still
-communicate by using an API tailored to asynchrounous programming. The example
-may not be the best, though:
+communicate by defining a callback the subprocess can call when it completes. 
+The example may not be the best, though:
 
 ```ruby
 class Inbox
-  def initialize
-    @msgs = []
-  end
-  
-  def msgs
-    @msgs
-  end
-
-  def recv(msg)
-    @msgs << msg
+  def recv(pid)
+    puts "'#{pid}' has finished!"
   end
 end
 inbox = Inbox.new
-IProcess.spawn!(2, Inbox.new) { Process.pid }
-sleep 0.1
-p inbox.msgs
+IProcess.spawn!(2, inbox) { Process.pid }
 ```
 
 __SERIALIZERS__

data/lib/iprocess.rb

@@ -54,9 +54,8 @@ class IProcess
   def self.spawn!(number_of, inbox, obj = nil, &worker)
     forks = fork number_of, obj, &worker
     forks.each do |subprocess|
-      Thread.new do
-        inbox.recv subprocess.result
-      end
+      t = Thread.new { inbox.recv subprocess.result }
+      at_exit { t.join }
     end
   end
 

data/lib/iprocess/version.rb

@@ -1,3 +1,3 @@
 class IProcess
-  VERSION = '5.0.5'
+  VERSION = '5.1.0'
 end

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: iprocess
 version: !ruby/object:Gem::Version
-  version: 5.0.5
+  version: 5.1.0
   prerelease: 
 platform: ruby
 authors:
@@ -9,7 +9,7 @@ authors:
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2013-01-12 00:00:00.000000000 Z
+date: 2013-02-24 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: ichannel