| michaelbryne | as in, i have a function that sets an array of options that I use for navigation tabs, and I want to use those options inside another controller |
| pstickne | bitsweat, right, a fork after the meat of RoR is loaded. |
| bitsweat | I've been trying that with the fcgi dispatcher |
| pstickne | bitsweat, cool |
| Rappermas | so i've decided that i'm just going to write my application and worry about replacing WEBrick later |
| bitsweat | it's nice for ez setup and maintenance mostly |
| michaelbryne | is there a better place to store these options than inside the controller? |
| bitsweat | hopefully moving it to mongrel, but that's more complex |
| pstickne | bitsweat, it seems like you'd need to do it after the DB schema is read then re-establish connections in the children? bitsweat, how is it working? |
| bitsweat | kinda half-assed yet :) |
| jeremydurham | Rappermas: good move |
| bitsweat | yeah you can choose where to fork |
| Rappermas | jeremydurham: sanity is returning already |
| bitsweat | just be sure to reconnect to the db and reopen the log |
| pstickne | Does Rack define a fcgi-like coupling? |
| bitsweat | yes |
| pstickne | bitsweat, have you done any tests on memory consumption/shared mem? |
| bitsweat | ruby gc means forking gives no memory advantage |
| pstickne | hmm. |
| bitsweat | since mark phase touches all objects |
| pstickne | that makes sense. |
| bitsweat | but spawning children is certainly faster |
| pstickne | but you still have the DB connection overhead; I suppose it could be pooled though |
| bitsweat | db connect is super fast unless you're using oracle |
| pstickne | okay then :) |
| bitsweat | and persisted for the child's lifetime anyway |
| pstickne | I wonder how bloody impossible it would be to make RoR (ruby) thread-safe |
| bitsweat | I hacked something together by hand then came across http://tmtm.org/ruby/prefork/ and am trying to migrate to that instead |
| yakkop | hi. have a rails app server, and need to create j2me client -- anyone aware of any rails like j2me frameworks? |
| jeremydurham | pstickne: it's happened before, so it can't be that bad... I'm sure it's mostly the libraries |
| pstickne | bitsweat, aiiiy! can you read Japanese? |
| bitsweat | not very hard.. the main reason Rails isn't thread safe is because it uses class variables within a single request that page machine-translates well plus all you need is the tarball :) AR is mostly thread safe and has tests to prove it |
| Sneaky_Bastard | AR ? |
| pstickne | ActiveRecord |