em_s3 0.0.1 → 0.0.2
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- data/.gitignore +1 -0
- data/README.md +9 -27
- data/em_s3.gemspec +3 -3
- data/lib/em_s3/version.rb +1 -1
- metadata +3 -4
- data/README +0 -11
data/.gitignore
CHANGED
data/README.md
CHANGED
@@ -1,29 +1,11 @@
|
|
1
|
-
#
|
1
|
+
# S3Interface
|
2
|
+
This is a general purpose S3 upload/download library using EM::Deferrables which can retry while accessing from S3. Who doesn't want to retry when they get a 5xx from S3?
|
2
3
|
|
3
|
-
|
4
|
+
# S3Agent
|
5
|
+
A serialization framework on top of S3Interface which could possibly occur when you are `put`ting objects in S3 in a reactor loop. Crude but works.
|
4
6
|
|
5
|
-
|
6
|
-
|
7
|
-
|
8
|
-
|
9
|
-
|
10
|
-
|
11
|
-
And then execute:
|
12
|
-
|
13
|
-
$ bundle
|
14
|
-
|
15
|
-
Or install it yourself as:
|
16
|
-
|
17
|
-
$ gem install em_s3
|
18
|
-
|
19
|
-
## Usage
|
20
|
-
|
21
|
-
TODO: Write usage instructions here
|
22
|
-
|
23
|
-
## Contributing
|
24
|
-
|
25
|
-
1. Fork it
|
26
|
-
2. Create your feature branch (`git checkout -b my-new-feature`)
|
27
|
-
3. Commit your changes (`git commit -am 'Added some feature'`)
|
28
|
-
4. Push to the branch (`git push origin my-new-feature`)
|
29
|
-
5. Create new Pull Request
|
7
|
+
# Caveats
|
8
|
+
* Doesn't (yet) run the event loop. I developed this when I was working on a Thin based app server. Future versions may have support for running an event loop.
|
9
|
+
* Works only for get_object and put_object. More methods coming soon.
|
10
|
+
* Do not define errbacks on instances of S3Interface. It uses errbacks to retry and __always__ succeeds and responds with an error code in case of an error.
|
11
|
+
* Feel free to fork and modify.
|
data/em_s3.gemspec
CHANGED
@@ -4,9 +4,9 @@ require File.expand_path('../lib/em_s3/version', __FILE__)
|
|
4
4
|
Gem::Specification.new do |gem|
|
5
5
|
gem.authors = ["Paul Victor Raj"]
|
6
6
|
gem.email = ["paulvictor@gmail.com"]
|
7
|
-
gem.
|
8
|
-
gem.
|
9
|
-
gem.homepage = ""
|
7
|
+
gem.summary = "Enables evented access to S3 get and put interface"
|
8
|
+
gem.description = gem.summary
|
9
|
+
gem.homepage = "http://github.com/paulvictor/em_s3"
|
10
10
|
|
11
11
|
gem.add_dependency('em-http-request', '>=1.0.2')
|
12
12
|
|
data/lib/em_s3/version.rb
CHANGED
metadata
CHANGED
@@ -1,7 +1,7 @@
|
|
1
1
|
--- !ruby/object:Gem::Specification
|
2
2
|
name: em_s3
|
3
3
|
version: !ruby/object:Gem::Version
|
4
|
-
version: 0.0.
|
4
|
+
version: 0.0.2
|
5
5
|
prerelease:
|
6
6
|
platform: ruby
|
7
7
|
authors:
|
@@ -27,7 +27,7 @@ dependencies:
|
|
27
27
|
- - ! '>='
|
28
28
|
- !ruby/object:Gem::Version
|
29
29
|
version: 1.0.2
|
30
|
-
description:
|
30
|
+
description: Enables evented access to S3 get and put interface
|
31
31
|
email:
|
32
32
|
- paulvictor@gmail.com
|
33
33
|
executables: []
|
@@ -38,7 +38,6 @@ files:
|
|
38
38
|
- .rvmrc
|
39
39
|
- Gemfile
|
40
40
|
- LICENSE
|
41
|
-
- README
|
42
41
|
- README.md
|
43
42
|
- Rakefile
|
44
43
|
- em_s3.gemspec
|
@@ -48,7 +47,7 @@ files:
|
|
48
47
|
- lib/em_s3/version.rb
|
49
48
|
- lib/s3_agent.rb
|
50
49
|
- lib/s3_interface.rb
|
51
|
-
homepage:
|
50
|
+
homepage: http://github.com/paulvictor/em_s3
|
52
51
|
licenses: []
|
53
52
|
post_install_message:
|
54
53
|
rdoc_options: []
|
data/README
DELETED
@@ -1,11 +0,0 @@
|
|
1
|
-
S3Interface :
|
2
|
-
This is a general purpose S3 upload/download library using EM::Deferrables which can retry while accessing from S3. Who doesn't want to retry when they get a 5xx from S3?
|
3
|
-
|
4
|
-
S3Agent :
|
5
|
-
A serialization framework on top of S3Interface which could possibly occur when you are `put`ting objects in S3 in a reactor loop. Crude but works.
|
6
|
-
|
7
|
-
Caveats :
|
8
|
-
* Doesn't (yet) run the event loop. I developed this when I was working on a Thin based app server. Future versions may have support for running an event loop.
|
9
|
-
* Works only for get_object and put_object. More methods coming soon.
|
10
|
-
* Do not define errbacks on instances of S3Interface. It uses errbacks to retry and __always__ succeeds and responds with an error code in case of an error.
|
11
|
-
* Feel free to fork and modify.
|