Yes we're going to put the LFC into a static file in a known location.
That location can be shared among multiple apps, although the SOLO deploy wizard will default to write a local copy out into the "lps/" subdirectory of the application home dir. Essentially, the SOLO deployer builds a local copy of the lps/includes tree and puts it in the same directory as the app, but those common files can be moved to a shared location by the developer by tweaking the paths in the html wrapper for the app. On 11/16/06, David Temkin <[EMAIL PROTECTED]> wrote:
I don't totally understand what's below, but is this an opportunity to put the LFC in its own place, so that if a single site uses more than SOLO app, they'll only have to load the LFC once, and that copy will be loaded from the browser cache for all apps? I think this is already true for server-deployed apps under DHTML (though not SWF). Correct? On Nov 16, 2006, at 5:56 AM, Phillip George Apley wrote: > Path decomposition summary: > > * Component Names: > > * host e.g. http://host/ > * LzServerBase e.g. /legals > * LzApplicationPath e.g. demos/amazon > * LzCommonResourcePath e.g. deploy/resources | "/" > > * Path Generation Formulas: > > * ar: application relative resource: HOST + / + > LzServerBase + LzApplicationPath + respath (page relative or > application relative) > * cr: server relative common resource: HOST + / + > LzServerBase + LzCommonResourcePath + respath (common library > relative) > * ap: absolute external path resource: respath (fully > qualified URL) (absolute, external URL) > * > * Path Examples: > * host serverbase > resourcebase path > * cr: http://localhost:8080 / > legals/ lps/components/lz/button.png > * cr: http://localhost:8080 /legals/ [deploy/ > resources/] lps/components/lz/button.png > * ar: http://localhost:8080 /legals/ [demos/ > amazon/] amazon.html > * ap: [] [] > [] http://somehost/somepath/file.png > > > > Phillip G. Apley > Senior Software Engineer > Platform Team > Laszlo Systems, Inc. > [EMAIL PROTECTED] > [EMAIL PROTECTED] > > maynard: 978-298-5210 > allston: 617-787-2831 > cell: 617-283-1717 > skype: phillipapley > > aim: phillipapley > jabber: [EMAIL PROTECTED] > irc: [EMAIL PROTECTED] > icq: 258643767 > > > Phillip G. Apley > Senior Software Engineer > Platform Team > Laszlo Systems, Inc. > [EMAIL PROTECTED] > [EMAIL PROTECTED] > > maynard: 978-298-5210 > allston: 617-787-2831 > cell: 617-283-1717 > skype: phillipapley > > aim: phillipapley > jabber: [EMAIL PROTECTED] > irc: [EMAIL PROTECTED] > icq: 258643767 > >
-- Henry Minsky Software Architect [EMAIL PROTECTED]
