Hi,
On Dec 21, 2005, at 8:14 AM, John W. wrote:
Guys,
I’m designing an application currently that will ultimately be
implemented
in either Rails or php5 (most likely Rails).
[snip]
issues a
request two seconds after this one that would require the same
objects, am
I forced to reload everything again, or is there a better way?
This scenario is pretty much exactly why I wrote xampl (first in
Java, then in Lisp, now in Ruby). There is a GPL version on
rubyforge: http://rubyforge.org/projects/xampl/. Well, there’s a
lot more to the ‘why xampl’ than that but anyway…
I’m working (in production but being actively developed) on a
relatively simple application that has something like 42 classes (and
who knows how many instances) that might get dragged in as you
describe. I have a larger application in production that has 120 such
classes, and another with 201. These are all Java applications as it
happens. I also have a Common Lisp application with 49 classes like
that. I’ve only been prototyping in Ruby so far, but I think the
smaller applications (40-49) would be more than feasible in Ruby. I’m
not completely sure how these would translate to tables in
ActiveRecord because I don’t know how many inter-object relationships
are supported by these applications (but there would be a lot,
certainly no less than 3 or 4 per object).
I am just now starting to look at how I might integrate xampl with
Rails. There are a number of possibilities that I can see, the
easiest (you can do this today) is to just use it for the Model but
you’ll lose the whole scaffolding part of Rails. This is an
unpleasant trade-off, and one that I think should be at least
partially addressable through modifications to xampl alone. On the
other hand, I would have a very difficult time using the CRUD
approach (even with all the help Rails provides) with the kinds of
applications I write, so I’d unhappily be willing to give up on the
scaffolding.
As an alternative, you might look into how to use Madeleine with
Rails (instiki does this). This might be a good solution if your
application fits the constraints of Madeleine.
And of course, there could be other solutions. As I say, I’m new to
Rails. I plead ignorance if I’ve ignored anything
I know serialization might work for this, but I’m concerned about
overhead.
I wouldn’t recommend this. You’d be far further ahead trying to use
the AR model as it now stands, or working with xampl.
Thanks in advance for your help in clarifying this dilemma.
Hmm. I don’t know if I clarified anything
Cheers,
Bob
John
Rails mailing list
[email protected]
http://lists.rubyonrails.org/mailman/listinfo/rails
Bob H. – blogs at http://www.recursive.ca/hutch/
Recursive Design Inc. – http://www.recursive.ca/
Raconteur – http://www.raconteur.info/