Good point. But for the first loading of the page it still makes a big difference, especially on slow connections. The difference for only the 3 mentioned files is 216 KiB already (with gzip compression), which can translate to several seconds wait time. In my case that does not matter, but for commercial sites reponse times are important.
Regards, Henrik Am 31.08.2016 um 18:22 schrieb Peter Kriens: > It was designed to support this using a debug flag but I never got around it. > It is also probably not that important because they ’should’ be cached and > compressed. We can provide the browser the information that it never expires > since a new bundle will have a new URL. > > Kind regards, > > Peter Kriens > >> On 31 aug. 2016, at 18:15, Henrik Niehaus <henrik.nieh...@gmx.de> wrote: >> >> I have created an issue for that: >> https://github.com/osgi/osgi.enroute.bundles/issues/67 >> >> Another question came up, while having a closer look at the web >> resources. I noticed that not the minified versions are served, but the >> "human readable" (for example angular and bootstrap). Is there a way to >> switch to the minified versions? I tried to change the annotation >> parameters: >> >> @RequireAngularWebResource(resource={"angular.min.js","angular-resource.min.js", >> "angular-route.min.js"}, priority=1000) >> >> But then the minified version are appended to *.js in addition to the >> human readable files, so the resulting content is even bigger. >> >> Regards, >> Henrik >> >> Am 31.08.2016 um 16:41 schrieb Peter Kriens: >>> Hmm, were cached and compressed. Can you file a bug? Especially which >>> version of the simple web provider you’re using. The latest version had a >>> few changes. >>> >>> Kind regards, >>> >>> Peter Kriens >>> >>>> On 31 aug. 2016, at 14:17, Henrik Niehaus <henrik.nieh...@gmx.de> wrote: >>>> >>>> I was playing around with enroute and the angular and bootstrap web >>>> resources. I noticed, that the concatenated files *.js and *.css are >>>> served uncompressed by Jetty. Especially the 1.6 MiB angular files take >>>> quite some time to load. >>>> >>>> How would you handle this in a production environment? Would you run >>>> Jetty behind an Apache proxy or is there a way to configure Jetty to run >>>> standalone and be production ready? Are there any articles or tutorials >>>> for that, because I didn't find much on that topic. >>>> >>>> Regards >>>> >>>> -Henrik >>>> >>>> _______________________________________________ >>>> OSGi Developer Mail List >>>> osgi-dev@mail.osgi.org >>>> https://mail.osgi.org/mailman/listinfo/osgi-dev >>> >>> _______________________________________________ >>> OSGi Developer Mail List >>> osgi-dev@mail.osgi.org >>> https://mail.osgi.org/mailman/listinfo/osgi-dev >> >> _______________________________________________ >> OSGi Developer Mail List >> osgi-dev@mail.osgi.org >> https://mail.osgi.org/mailman/listinfo/osgi-dev > > > _______________________________________________ > OSGi Developer Mail List > osgi-dev@mail.osgi.org > https://mail.osgi.org/mailman/listinfo/osgi-dev _______________________________________________ OSGi Developer Mail List osgi-dev@mail.osgi.org https://mail.osgi.org/mailman/listinfo/osgi-dev
