enigmamachine 0.4.1 → 0.4.2

data/README.rdoc

@@ -53,7 +53,8 @@ receive the video. When the upload is complete, make an HTTP call something like
 
 with the params:
 
- "video=/foo/bar/blah.mp4" # the full path to a file on your local filesystem
+ "video[file]=/foo/bar/blah.mp4" # the full path to a file on your local filesystem
+ "video[callback_url]=http://example.org/call/back/id" # an optional callback url
  "encoder_id=1" # the id of an encoder defined in your enigmamachine database
 
 The enigmamachine will run all encoding tasks on the video, while your web
@@ -66,6 +67,10 @@ protected by HTTP basic auth.  By default, the username is
 <i>admin</i> and the password is <i>admin</i>.  You can change the username and
 password in the config.yml file which will be generated on first use.
 
+When a video has finished encoding, the main web application might want to know.
+The optional video[callback_url] parameter tells enigmamachine to execute a GET
+request to the callback url when video encoding is complete.
+
 Programmatic requests in Ruby might look something like this:
 
 # enigma_client.rb:

data/VERSION

@@ -1 +1 @@
-0.4.1
+0.4.2

data/enigmamachine.gemspec

@@ -5,7 +5,7 @@
 
 Gem::Specification.new do |s|
   s.name = %q{enigmamachine}
-  s.version = "0.4.1"
+  s.version = "0.4.2"
 
   s.required_rubygems_version = Gem::Requirement.new(">= 0") if s.respond_to? :required_rubygems_version=
   s.authors = ["Dave Hrycyszyn"]

metadata

@@ -1,13 +1,13 @@
 --- !ruby/object:Gem::Specification 
 name: enigmamachine
 version: !ruby/object:Gem::Version 
-  hash: 13
+  hash: 11
   prerelease: false
   segments: 
   - 0
   - 4
-  - 1
-  version: 0.4.1
+  - 2
+  version: 0.4.2
 platform: ruby
 authors: 
 - Dave Hrycyszyn