-Steven--
You received this message because you are subscribed to the Google Groups "MagLev Discussion" group.
To post to this group, send email to maglev-d...@googlegroups.com.
To unsubscribe from this group, send email to maglev-discuss...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/maglev-discussion?hl=en.
On Tuesday, 15 January, 2013 at 4:12 PM, Jesse Cooke wrote:
-Mcommit will commit from the command line, which should do what you want it to do (essentially wraps your script in a persistent_do block & commits just after)
What changes are you making to your classes? Adding, changing, or removing methods/attrs?
Examples will definitely help come up with solutions.Persistence is like _really_ persistent -- by reachability. Getting rid of an object so it can be garbage collected means eliminating all persistent references. It's also possible for objects to hold on to old class references. At least it's easy to figure that out programmatically since objects have an actual identity.
I was curious about your need for multiple stones. Was it for multiple apps that don't share any data? Isolation? Would logging in as a different user possibly help? Or performance/scalability? Note that multiple VMs should consume multiple cores.
Examples will definitely help come up with solutions.�
Persistence is like _really_ persistent -- by reachability. Getting rid of an object so it can be garbage collected means eliminating all persistent references. It's also possible for objects to hold on to old class references. At least it's easy to figure that out programmatically since objects have an actual identity.
This is what we want. We are going to have to come up with a way to get old instances of objects migrated to their new definitions, though� But we'll burn that bridge when we get to it, I guess.I was curious about your need for multiple stones. Was it for multiple apps that don't share any data? Isolation?�Would logging in as a different user possibly help?�Or performance/scalability?��Note that multiple VMs should consume multiple cores.�
The short answer is isolation. What I had in mind was one per "environment" in the Rails sense of the term. So when I'm running my tests, it doesn't mess with data that I need for other purposes.
-Steven
-- Monty
On Jan 15, 2013, at 12:20 PM, "Steven R. Baker" <ste...@stevenrbaker.com> wrote:
On Tuesday, 15 January, 2013 at 4:12 PM, Jesse Cooke wrote:
-Mcommit will commit from the command line, which should do what you want it to do (essentially wraps your script in a persistent_do block & commits just after)I'll look at this. Thanks!What changes are you making to your classes? Adding, changing, or removing methods/attrs?Yes. I know there are likely other issues with this; I'm going to have to work out some small, repeatable examples of the things I'm running into.
-Steven
�
--------------------------------------------
Jesse Cooke ::�N-tier Engineer
jc00ke.com�/ @jc00ke
I talked with Peter about persisting an entire Rails app & he said Rails maintains some open file descriptors that would prevent it from being persisted.
Sinatra, on the other hand... not sure.