Jeppe probably we can combine the two proposals. Perhaps something
like:

<lift:css name="mycss.css, some_other.css. /classpath/baz.css" />

thus Lift could generate:

<link rel="stylesheet" type="text/css" href="compound_2434rfe34534.css?
i784yrfiuhferfhweir57=_"/>

compound_2434rfe34534.css is a synthetic name that would contain the
mycss.css, some_other.css. /classpath/baz.css concatenated. Same thing
for JS. This content could potentially be compressed.

I can open a ticket and start looking into this.

Br's,
Marius

On 12 feb., 20:53, Jeppe Nejsum Madsen <[email protected]> wrote:
> On Fri, Feb 12, 2010 at 7:28 PM, Marius <[email protected]> wrote:
> > Oh yes I did and I hate it. Ironically I was about to propose a
> > solution for this.
>
> > instead of
>
> > <link rel="stylesheet" type="text/css" href="mycss.css"/>
>
> > do something like:
>
> > <lift:css name="mycss.css" />
>
> > this would render:
>
> > <link rel="stylesheet" type="text/css" href="mycss.css?
> > i784yrfiuhferfhweir57=_"/>
>
> > the query string parameter would be generated at application start-up.
> > If you update you css/js and restart the application the browser will
> > refresh it. Potentially generating the random query string param could
> > be a LiftRules function that by default generates a sequence once per
> > application time. Thus you could potentially set your own function
> > that reads this for a config file?
>
> > Similarly <lift:js name="myjs.js"/> would do the same.
>
> I had similar thoughts sometime ago, but haven't looked at it since then:
>
> http://groups.google.com/group/liftweb/browse_thread/thread/1130ce4f9...
>
> For me, the real benefit would be combining many requests into one and
> setting a future "Expires" date but still be sure that all artifacts
> will be updated correctly.
>
> /Jeppe

-- 
You received this message because you are subscribed to the Google Groups 
"Lift" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/liftweb?hl=en.

Reply via email to