day_planner 0.0.13 → 0.0.13.1

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA1:
-  metadata.gz: 2f22f16d1b49963c3290b1e6a8e91d3f4dfd1797
-  data.tar.gz: e6514798c238eab344078c3d2ca75fa418ea2a65
+  metadata.gz: 930def21830db638cd84df9a141e72df1b291d69
+  data.tar.gz: dbe3655ab9337d45eff1ec2a58f5d1a45349fc8e
 SHA512:
-  metadata.gz: d3b4905a664d1695fb2a6ffaa828da69822ef077f5537d50cf2f226d14f57b3a08a47e1b618aab07711edccf6edc5c8694f50fd244f8e648e3243c59b4e70d6f
-  data.tar.gz: 013cb5b39b8c68cb3ba8b283f63c1d8ab5ac19efb8adbf9f991bcd855e9bc34413686e073f87bf1232df13951fb69a3977f7e35d48c49f5f7f304fb097c702dc
+  metadata.gz: f281ee7c192aa5d4616ca697f1e188692fec1fb79947b3c34a15a3a34eeb23c3ae435a065dbef7e389c4e3dd55c173f383b58cf752777c1860d38d1093e83684
+  data.tar.gz: ebe32d136206795ab5a19a41178a3dc90de954a09946f736f5572755c019a772ee382d9cf799568ad6b546ac04785cd8e9568995a92b5f3b631d7ea6b3d2f694

data/README.md

@@ -4,7 +4,7 @@ Day Planner is a simple tool to manage in-process execution of scheduled tasks.
 
 I wrote this because I needed a simple, lightweight tool to schedule small, light tasks on an application running on Heroku, without the extra cost of a dedicated clock process to handle it, but executing more frequently than Heroku's free scheduler permits.
 
-Schedule management is in a thread of its own; each scheduled task is run in a thread as well, meaning that lots of long-running tasks could result in lots of threads. Ruby 2.0's handling of threading is improved over the 1.9 branch, so I require that as a minimum, but I obviously can't guarantee that you won't encounter situations in which poorly behaved tasks block your application's main thread. If you want assurances against that, use any of the other tools (did I mention [Clockwork](http://rubygems.org/gems/clockwork)?)
+Schedule management is in a thread of its own; scheduled tasks are run in the same thread (I was spawning separate threads for them, but it seemed to be causing issues with database utilization on Heroku). Ruby 2.0's handling of threading is improved over the 1.9 branch, so I require that as a minimum, but I obviously can't guarantee that you won't encounter situations in which poorly behaved tasks block your application's main thread. If you want assurances against that, use any of the other tools (did I mention [Clockwork](http://rubygems.org/gems/clockwork)?)
 
 ## Installation
 

data/lib/day_planner/version.rb

@@ -2,7 +2,7 @@ module DayPlanner
 	MAJOR = 0
 	MINOR = 0
 	TINY  = 13
-	BUILD = nil
+	BUILD = 1
 
   VERSION = [MAJOR, MINOR, TINY, BUILD].compact.join(".")
 end

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: day_planner
 version: !ruby/object:Gem::Version
-  version: 0.0.13
+  version: 0.0.13.1
 platform: ruby
 authors:
 - Damon Siefert
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2013-12-28 00:00:00.000000000 Z
+date: 2013-12-29 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: bundler