I'm getting undefined method `call' because the next piece in the middleware chain has an instance method "call" but no class method "call". I'm confused about how this is supposed to work.
I would love to see rack-worker functioning, but I cannot get it to do so. Part of its process is to serialize env to json, and obviously objects like rack.input (part of the rack spec) are no longer functional. The env just can't be serialized and unserialized in a valid enough way for other basic middleware or something like rails to work with this. I don't see how it ever functioned. Am I confused?
I've been using this with Sinatra apps and straight Rack apps (look at the tests) and havent' used this middleware in a Rails app just yet. I was hoping that because Rails 3 is "rack compliant" it should have been able to just drop in.
You can ignore rack.input for GET requests (its for POST bodys).
i think you're right about this -- that line should look like:
status, headers, body = app.new.call(env.merge('rack.worker_qc' => true))
right now having some trouble running the tests again, but will release as soon as i have it tested
if you look at the Rack docs, they say you should define ::call at the class level
but i think the about.com docs places show it as an instance method
this supports both:
looking to release this soon