No, for the reason you state beow -- shared LFC across multiple apps.
A separate LFC should not affect performance since one additional HTTP
fetch using keep-alive should have essentially zero overhead.
I'm hoping we can do this for SWF9 as well, but I assume that is a
completely separate discussion. And someday we can do this for things
like component libraries.
On Jul 9, 2008, at 11:59 AM, Henry Minsky wrote:
http://www.openlaszlo.org/jira/browse/LPP-4359
I was looking at this bug report about producing a SOLO dhtml app, and
it occurred to me, we make
the dev-console into a single .js file, would there be any advantage
to making the SOLO DHTML deployer
do the same thing; concatenate the DHTML LFC and the app into a single
.js file?
I guess the advantage of keeping them separate is theoretically the
browser could cache the LFC if you
run multiple apps, but is it logistically better for app deployers to
have a single file/. It seems to me it doesn't
make that much difference, because SOLO apps tend to need a bunch of
support files in
a directory structure anyway...
--
Henry Minsky
Software Architect
[EMAIL PROTECTED]
