From: Frank Ficnar <firstname.lastname@example.org> To: Rack Development <email@example.com> Subject: Re: Rack Application Initializes On Every Request Date: Wed, 28 Dec 2011 11:38:12 -0800 (PST) [thread overview] Message-ID: <firstname.lastname@example.org> (raw) In-Reply-To: <54F669AE-14FD-425A-B6CE-BBC4D893D5ED@gmail.com> I'm not using Rack::Builder directly ... unless it's being used behind the scenes. I've got a config..ru as follows ... #\ --warn --port 8008 --pid ./rack.pid require 'rubygems' require 'bundler/setup' require 'rack' require 'ruby_app/rack/application' require 'ruby_app/rack/route' require 'ruby_app/version' use Rack::ShowExceptions use Rack::Session::Pool use Rack::Reloader use Rack::ContentLength map '/favicon.ico' do run Rack::File.new(File.join(RubyApp::ROOT, %w[resources favicon.ico])) end map '/ruby_app/resources' do run Rack::File.new(File.join(RubyApp::ROOT, %w[resources])) end map '/' do use RubyApp::Rack::Application run RubyApp::Rack::Route.new end ... where RubyApp is my middleware/application. During development the server is started via ... Rack::Server.start(:config => '(path to config.ru)') It's the RubyApp::Rack::Application class that I've observed being initialized on every request. I haven't checked but I suspect the RubyApp::Rack::Route class is as well. Thanks for your help. Frank On Dec 28, 1:35 pm, James Tucker <jftuc...@gmail.com> wrote: > Can you provide some more information? > > Rack doesn't instantiate anything itself. > > If you're using Rack::Builder, and you're talking about a middleware, then it's likely you forgot to call #to_app on the Builder instance before passing it to the handler. > > On Dec 28, 2011, at 11:43 AM, Frank Ficnar wrote: > > > > > > > > > Is it normal that my 'initialize' method is called on every request to > > my Rack application (non-Rails)? > > > Rack' 1.3.5 didn't do this ... it started with the 1.4.0 update. > > > Frank
next prev parent reply other threads:[~2011-12-28 19:38 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-12-28 15:43 Frank Ficnar 2011-12-28 18:35 ` James Tucker 2011-12-28 19:38 ` Frank Ficnar [this message] 2011-12-29 4:47 ` Frank Ficnar
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-list from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style List information: https://groups.google.com/group/rack-devel * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --email@example.com \ --firstname.lastname@example.org \ --subject='Re: Rack Application Initializes On Every Request' \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: link
Code repositories for project(s) associated with this inbox: https://80x24.org/mirrors/rack.git This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).