Re: [RFC/PATCH] Add Rack::Builder#warmup method for app preloading.

[Eric Wong <normalperson@yhbt.net>]

Eric Wong <normalperson@yhbt.net> wrote:
> James Tucker <jftucker@gmail.com> wrote:
> > Yeah, Builder#call leads to mistakes all the time and then people claiming
> > performance sucks. I don't think the simple use case there ever helped.
> 
> Just curious, is this in test suites or code running on live servers?
> I can't imagine there are many one-off webservers existing and using
> that directly...

Answering my own question, the "map" directive in Builder seems to
trigger Builder#to_app in every single request.

It looks like map completely defeats warmup and preloading...

-------------------------------8<-----------------------------
require 'rack/lobster'
class Wtf
  def initialize(app)
    # this prints every single request :<
    p "#$$ #{Time.now} initialized"
    @app = app
  end
  def call env
    @app.call(env)
  end
end

map "http://example.com/" do
  use Wtf
  run Rack::Lobster.new
end
-------------------------------8<-----------------------------
(tested with "rackup -s webrick", too, so none of my own broken server
 code running)

But yeah, extensive use of map on *.bogomips.org and *.yhbt.net
now that I've switched that hole thing over to yahns...

-- 

--- 
You received this message because you are subscribed to the Google Groups "Rack Development" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rack-devel+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.