On Mon, Nov 15, 2010 at 4:22 PM, Ciancetta, Jesse E. <[email protected]> wrote: > Hi, > > I noticed that it doesn't appear that people are using the concat and proxy > servlets in the wild and I was wondering if anyone might be able to provide > any insight into why that is. I looked at all the resources loaded for an > iframed gadget on LinkedIn, iGoogle and a local instance of Atlassian JIRA > and I didn't see any references to /concat or /proxy -- so it seems unless > I'm missing something they aren't being used. > > I was also wondering if anyone might be able to share any high level > performance tuning tips for a production Java Shindig installation. I've > already tuned the caches to make sure I have enough capacity in them and have > done some JVM tuning, but I'm wondering if there are other things I should > also be doing.
At nk.pl we also use concat/proxy servlets (we have content rewriting turned on by default). However, application developers can turn those off in the gadget spec. From our practice, there are mainly two reasons for those to be disabled: 1. They blame them for caching their static content. Which is usually wrong as the browser would cache it anyway. 2. They make some typo, for example in CSS file and blame those servlets for truncating it. This is again wrong as browsers are usually more permissive, but this doesn't mean that the CSS file in question is working correctly. Also it happens that some developers provide broken content-rewrite in gadget spec (for example using .* for include-url instead of *) which also disables content rewriting (and they are too lazy to take notice/fix this). -- Janusz Dziemidowicz http://nk.pl
