On Sat, Sep 02, 2006 at 05:34:08PM -0000, DHH wrote:
Currently, I believe components just have some performance issues. I’d
encourage you to benchmark with and without to see whether it matters
in your case. And then be on the lookout for other/better ideas that we
could possibly do this. As well as keeping in mind that components are
not a general strategy for compartmentalizing things in Rails, unless
they have this portlet-type flavor we’re discussing.
Components have had performance issues in EVERY web platform I’ve
used, but usually that’s related to the overhead of an additional
request/ssi, instantiating the execution stack, or something related.
I suspect (but haven’t dug into the code to confirm) that the right
way to approach this might be to stick a continuation somewhere in the
rendering path to save all of that setup and use it later to execute
an additional action/view pair.
** Expert Technical Project and Business Management
**** System Performance Analysis and Architecture
****** [ http://www.adamfields.com ]