doc: avoid documenting internals on RDoc website

Since we suck at building websites, we just rely on RDoc as a
website builder.  And since Rainbows! is an application server
(and not a programming library), our internal API should be of
little interest to end users.

Anybody interested in Rainbows! (or any other project) internals
should be reading the source.

1 files changed, 2 insertions, 2 deletions

diff --git a/lib/rainbows/sendfile.rb b/lib/rainbows/sendfile.rb
index 3f82047..8d9b46e 100644
--- a/lib/rainbows/sendfile.rb
+++ b/lib/rainbows/sendfile.rb
@@ -57,7 +57,7 @@ class Sendfile < Struct.new(:app)
   # Body wrapper, this allows us to fall back gracefully to
   # +each+ in case a given concurrency model does not optimize
   # +to_path+ calls.
-  class Body < Struct.new(:to_path)
+  class Body < Struct.new(:to_path) # :nodoc: all
 
     def self.new(path, headers)
       unless headers['Content-Length']
@@ -76,7 +76,7 @@ class Sendfile < Struct.new(:app)
     end
   end
 
-  def call(env)
+  def call(env) # :nodoc:
     status, headers, body = app.call(env)
     headers = HH.new(headers)
     if path = headers.delete('X-Sendfile')