If I understand correctly, Mongrel and Passenger start multiple
instances of the Rails app, but these are long-lived. The app
instance is not created for each request and then destroyed.
On Dec 15, 5:43 pm, PierreW
<wamre...-gM/Ye1E23mwN+BqQ9rBEUg@public.gmane.org>
wrote:> Hi guys,
>
> I am new to Rails, so if my assumptions below are completely wrong,
> please do let me know.
>
> My app needs to load a shared library. I use Ruby/DL to do this.
> My understanding of Rails is since it''s single-threaded, the way
to
> deploy an app is to use HTTP proxying to send requests that should be
> handled by Rails to one of any number of back-end application
> processes.
> Does it mean the shared library will be loaded by every single
> application process? This library is very big (and in fact takes a lot
> of time to load), hence my concern. If my assumption is correct, it
> means the app will grow far too big. Is there any way to handle this?
>
> Thanks!
> Peter
--
You received this message because you are subscribed to the Google Groups
"Ruby on Rails: Talk" group.
To post to this group, send email to
rubyonrails-talk-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
To unsubscribe from this group, send email to
rubyonrails-talk+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/rubyonrails-talk?hl=en.