README.md in futuroscope-0.1.3 vs README.md in futuroscope-0.1.4
- old
+ new
@@ -1,10 +1,11 @@
# Futuroscope
[](http://badge.fury.io/rb/futuroscope)
[](https://travis-ci.org/codegram/futuroscope)
-[](https://gemnasium.com/codegram/futuroscope)
+[](https://codeclimate.com/github/codegram/futuroscope)
[](https://coveralls.io/r/codegram/futuroscope)
+[](https://gemnasium.com/codegram/futuroscope)
Futursocope is a simple library that implements futures in ruby. Futures are a
concurrency pattern meant to help you deal with concurrency in a simple way.
It's specially useful when working in Service Oriented Architectures where HTTP
@@ -14,19 +15,21 @@
You can learn more about futures here in this excellent article from @jpignata:
[Concurrency Patterns in Ruby:
Futures](http://tx.pignata.com/2012/11/concurrency-patterns-in-ruby-futures.html)
-In Futuroscope, futures are instanciated with a simple ruby block. The future's
+In Futuroscope, futures are instantiated with a simple ruby block. The future's
execution will immediately start in a different thread and when you call a
method on in it will be forwarded to the block's return value.
If the thread didn't finish yet, it will block the program's execution until
-it's finished. Otherwise, it will immediataly return its value.
+it's finished. Otherwise, it will immediately return its value.
Futuroscope is tested on `MRI 1.9.3`, `MRI 2.0.0`, `Rubinius (1.9)` and `JRuby (1.9)`.
+Check out [futuroscope's post on Codegram's blog](http://blog.codegram.com/2013/5/new-gem-released-futuroscope) to get started.
+
## Installation
Add this line to your application's Gemfile:
gem 'futuroscope'
@@ -120,11 +123,11 @@
You should never add **side-effects** to a future. They have to be thought of
like they were a local variable, with the only outcome that they're returning a
value.
You have to take into account that they really run in a different thread, so
-you'll be potentially accessing code in parallel that could not be threadsafe.
+you'll be potentially accessing code in parallel that could not be thread-safe.
If you're looking for other ways to improve your code performance via
concurrency, you should probably deal directly with [Ruby's
threads](http://ruby-doc.org/core-2.0/Thread.html).
@@ -161,5 +164,9 @@
1. Fork it
2. Create your feature branch (`git checkout -b my-new-feature`)
3. Commit your changes (`git commit -am 'Add some feature'`)
4. Push to the branch (`git push origin my-new-feature`)
5. Create new Pull Request
+
+
+[](https://bitdeli.com/free "Bitdeli Badge")
+