Keep in mind that the load error might be for some library required by the handler, not the handler itself.
… to load, take into account that this ruby file might register the handler properly. This basically would allow moving the Thin handler into the Thin gem and still supporting `rackup -s thin`. Also, when using Rack::Handler.register, call #to_s on both arguments. This allows, besides passing a symbol for `server`, passing a class or module as `klass` argument, see the included test case for an example.
Signed-off-by: Joshua Peek <firstname.lastname@example.org>
Made it so that it only accepts FullyCapsedClassNames for unregistered handlers as per suggestions in #rack irc channel. Signed-off-by: Michael Fellinger <email@example.com>
…on failure instead of nil under the principle of obvious failure. Signed-off-by: Michael Fellinger <firstname.lastname@example.org>
…make it possible for the responsibility for handler definition to be on the people writing servers without making life difficult for the user. ie. 'gem install thin', if thin includes its rack adapter, would make 'rackup -s thin' just work, which is how it should be. Signed-off-by: Michael Fellinger <email@example.com>