mdub / sham_rack
- Source
- Commits
- Network (1)
- Issues (0)
- Downloads (2)
- Wiki (1)
- Graphs
-
Branch:
master
| name | age | message | |
|---|---|---|---|
| |
.gitignore | Wed Jun 03 04:20:50 -0700 2009 | |
| |
CHANGES.markdown | Fri Jan 15 03:34:26 -0800 2010 | |
| |
README.markdown | Fri Nov 27 04:38:02 -0800 2009 | |
| |
Rakefile | Fri Jan 15 01:31:37 -0800 2010 | |
| |
benchmark/ | Sat Jun 27 05:05:33 -0700 2009 | |
| |
lib/ | Sat Jan 09 08:32:19 -0800 2010 | |
| |
sham_rack.gemspec | Fri Jan 15 03:37:53 -0800 2010 | |
| |
spec/ | Fri Nov 27 01:24:18 -0800 2009 |
README.markdown
ShamRack
ShamRack plumbs Net:HTTP into Rack.
What's it for, again?
Well, it makes it easy to stub out external (HTTP) services, which is handy in development and testing environments, or when you want to test your HTTP client code.
You can also use it to test your Rack application (or Sinatra, or Rails, or Merb) using arbitrary HTTP client libraries, to check interoperability. For instance, you could test your app using:
all without having to boot it in a server.
Installing it
gem install sham_rack
Using it
A simple inline application
require 'sham_rack'
ShamRack.at("www.example.com") do |env|
["200 OK", { "Content-type" => "text/plain" }, "Hello, world!"]
end
require 'open-uri'
open("http://www.example.com/").read #=> "Hello, world!"
Sinatra integration
ShamRack.at("sinatra.xyz").sinatra do
get "/hello/:subject" do
"Hello, #{params[:subject]}"
end
end
open("http://sinatra.xyz/hello/stranger").read #=> "Hello, stranger"
Rackup support
ShamRack.at("rackup.xyz").rackup do
use Some::Middleware
use Some::Other::Middleware
run MyApp.new
end
Any old app
ShamRack.mount(my_google_stub, "google.com")
What's the catch?
- Your Rack request-handling code runs in the same Ruby VM, in fact the same Thread, as your request.
