Hi, what is the preferd way to configure/start mongrel? [ ] with Mongrel::Configurator => HttpServer [ ] @var = HttpServer.new(...) @var.run I ask because the only debug methode i have found was in Mongrel::Configurator ;-) @Zed: are you also subscribed on nitro list?! regards Alex
On Sat, 2006-08-05 at 10:59 +0200, Alexander Lazic wrote:> Hi, > > what is the preferd way to configure/start mongrel? > > [ ] with Mongrel::Configurator => HttpServer > [ ] @var = HttpServer.new(...) @var.run >Use the Configurator since it''s simpler, but if you have NIH syndrome like rails-core you can do it all yourself with the HttpServer directly.> I ask because the only debug methode i have found was in > Mongrel::Configurator ;-) >Well, the configurator is a DSL for configuring a Mongrel server (even with multiple ports), so all you need to do is take a look at the code and see how debug is implemented.> @Zed: are you also subscribed on nitro list?! >Yep, I troll the nitro list too. -- Zed A. Shaw http://www.zedshaw.com/ http://mongrel.rubyforge.org/ http://www.railsmachine.com/ -- Need Mongrel support?
On Sam 05.08.2006 09:44, Zed Shaw wrote:>On Sat, 2006-08-05 at 10:59 +0200, Alexander Lazic wrote: > >Use the Configurator since it''s simpler, but if you have NIH syndrome >like rails-core you can do it all yourself with the HttpServer >directly.Sorry but what is the ''NIH syndrome''?!>> I ask because the only debug methode i have found was in >> Mongrel::Configurator ;-) > >Well, the configurator is a DSL for configuring a Mongrel server (even >with multiple ports), so all you need to do is take a look at the code >and see how debug is implemented.With multiple ports, i have look into the mongrel/configurator.rb but the as i understand the source with :port i can only use one port or do you mean in a for-loop outside the listerners?!>> @Zed: are you also subscribed on nitro list?! > >Yep, I troll the nitro list too.;-) Regards Alex
On Sat, 2006-08-05 at 19:27 +0200, Alexander Lazic wrote:> On Sam 05.08.2006 09:44, Zed Shaw wrote: > >On Sat, 2006-08-05 at 10:59 +0200, Alexander Lazic wrote: > > > >Use the Configurator since it''s simpler, but if you have NIH syndrome > >like rails-core you can do it all yourself with the HttpServer > >directly. > > Sorry but what is the ''NIH syndrome''?!Not Invented Here Syndrome. Means people like to go implement their own versions of stuff not because the current one has deficiencies but because they think they''re smarter and obviously anything someone else implements must be crap. The problem with NIH isn''t re-implementing stuff (Mongrel does this), the problem with it is people who have NIH syndrome just immediately assume the previous author was an asshole/idiot/moron/shitbag/etc. and they don''t try to understand the motivation for the current implementation. Eventually what happens is they end up implementing the exact same thing but in a different style because they encounter all the same problems and use all the same basic solutions. Then they waste a bunch of work on something that isn''t really better, just different. In other words, just use Configurator, but do it like RailsConfigurator where Nitro specific stuff is done in a subclass. Trying to do it all yourself defeats the stuff I''ve already figured out. -- Zed A. Shaw http://www.zedshaw.com/ http://mongrel.rubyforge.org/ http://www.railsmachine.com/ -- Need Mongrel support?
On Sam 05.08.2006 10:44, Zed Shaw wrote:>On Sat, 2006-08-05 at 19:27 +0200, Alexander Lazic wrote: > >> Sorry but what is the ''NIH syndrome''?! > >Not Invented Here Syndrome. Means people like to go implement their >own versions of stuff not because the current one has deficiencies but >because they think they''re smarter and obviously anything someone else >implements must be crap.Aha this one, it''s a nice abbreviation, i never heard it ;-)>In other words, just use Configurator, but do it like RailsConfigurator >where Nitro specific stuff is done in a subclass. Trying to do it all >yourself defeats the stuff I''ve already figured out.Well do you mean to add a lib/mongrel/nitro.rb intro mongrel?! Sorry but i''am not sure that i understand your right?! Regards Alex
On Sat, 2006-08-05 at 19:59 +0200, Alexander Lazic wrote:> On Sam 05.08.2006 10:44, Zed Shaw wrote: > >In other words, just use Configurator, but do it like RailsConfigurator > >where Nitro specific stuff is done in a subclass. Trying to do it all > >yourself defeats the stuff I''ve already figured out. > > Well do you mean to add a lib/mongrel/nitro.rb intro mongrel?! > > Sorry but i''am not sure that i understand your right?!That could be the end result, and I''m willing to help to do that. What I actually mean is instead of hand coding your own configuration script, use the features in Configurator. Just look at RailsConfigurator. Please? :-) -- Zed A. Shaw http://www.zedshaw.com/ http://mongrel.rubyforge.org/ http://www.railsmachine.com/ -- Need Mongrel support?
On Sam 05.08.2006 11:03, Zed Shaw wrote:>On Sat, 2006-08-05 at 19:59 +0200, Alexander Lazic wrote: >> >> Well do you mean to add a lib/mongrel/nitro.rb intro mongrel?! >> >> Sorry but i''am not sure that i understand your right?! > >That could be the end result, and I''m willing to help to do that. What >I actually mean is instead of hand coding your own configuration >script, use the features in Configurator.Wow i''am very suprised about this to hear *baff* ;-))>Just look at RailsConfigurator. Please? :-)Thats the point which i have thought to start ;-)) As you may assume i like to read the source ;-) About the question on nitro list about mongrel starts rails and nitro starts mongrel, what is the *better* way?! I think we should also ask george what he want, shouldn''t we? regards Alex