Rack

[dcu]

hi,

I ported your project to rack and provided both rack app(FakeS3::App and middleware FakeS3::Servlet).
reading is more than 2x faster
uploading is slightly slower

I switched default server to thin because webrick+rack fails when a PUT/POST request doesn't have body. (it's rack's handler fault)

[mferrier]

+1

[jubos]

This looks interesting. Does thin require a c compiler to install? I am keen on keeping Fake S3 to only require pure ruby gems to make portability easy. Is the rack webrick issue going to be fixed upstream?

[mferrier]

Removed thin dependency and sent pull request ricodigo#1

[elia]

@jubos anything I can help to make this happen?

[jubos]

I think it is a good idea, but just was initially worried about the additional complexity and pulling in another dependency. What is the use case for having FakeS3 as a rack app?

[elia]

I'm using it in conjunction with rack-streaming-proxy to have local s3 with a fallback on production to serve uploaded images in a rails app.

If you're worried about the additional dependency I suggest to just leave it out, but still provide an app conforming to the rack interface.

[elia]

ping

[pickhardt]

Closing because this was fixed. See #45 (I interpret the thumbs up to mean he acknowledges it worked.)