This looks a bit complex: http://www.samaxes.com/2009/05/combine-and-minimize-javascript-and-css-files-for-faster-loading/
but its an example of how other people have handled combining css and javascript files. On Feb 12, 4:11 pm, Jeppe Nejsum Madsen <je...@ingolfs.dk> wrote: > On Fri, Feb 12, 2010 at 10:04 PM, Alex Black <a...@alexblack.ca> wrote: > >> Yes, that's how it should work if everything was configured correctly > >> (which I think it wasn't for the OP) > > > Heh, I'm the OP. > > Ahh sorry :-) > > > The other option is say "you can cache this for like the next hour" > > but every time you fetch it, you can tell me when you last got it > > (conditional GET), and I won't send it to you if it hasn't changed > > (304 not modified). This results in more requests, but no need for > > unique filenames or anything, instead if the file changes then the > > server will serve it up to whoever needs it. > > But it's the "more requests" part I'm not interested in :-) For a > moderately complex page, there can easily be 20+ requests for > images/css/js etc. I would like to avoid that if possible. > > /Jeppe -- You received this message because you are subscribed to the Google Groups "Lift" group. To post to this group, send email to lift...@googlegroups.com. To unsubscribe from this group, send email to liftweb+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/liftweb?hl=en.
