> Does anybody have analized and alternative approach which would > consist on walking load_path before anything to generate Ruby builtin > autoload calls?
I believe the mod_rails guys do this for their system, it allows the copy-on-write stuff to only store one copy of all of your apps classes. So there are definitely people trying it out. The difference is that they're still able to use the const_missing stuff in the child processes. As discussed in ticket #9155 there's no way this can behave in a deterministic manner with multiple threads requiring classes. So preloading before spawning threads is really the only safe option, taking the stuff from Hongli and co as a starting point -- Cheers Koz --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/rubyonrails-core?hl=en -~----------~----~----~----~------~----~------~--~---
