Re: container "accel"

Yes, you can apply multiple rewriters to the http response. This is currently made possible by specifying a list of rewirters to be applied through AccelResponseRewriterRegistry

Re: container "accel"

i'm guessing that the accelerators are not mutually exclusive and that you could use more than one for a given request. Is this accurate? If so, maybe what we should be considering is some kind of strategy that allows you to register which accel handlers get used then use guice to put them together

Re: container "accel"

Hi Chirag Sorry for the late response, i have been chillaxing for a while now. The general purpose of accel is to provide a framework for content acceleration. The aim is to be able to speed up web pages without changing their functionality. A web publisher can always rewrite his page to speed it

Re: container "accel"

Hi Gagandeep, I was wondering how accel distinguishes itself from other HTTP reverse cache proxies such as squid, apache traffic server, and varnish? Squid and ATS both implement HTTP cache-control extensions such as http-stale-while-revalidate/http-stale-while-error. > Currently the only rewri

Re: container "accel"

Hi Gerald Sorry for the late response. Currently the only rewriter that accelerates web pages is ProxyingContentRewriter. It proxies all the resources through shindig and concatenates consecutive javascript and css resources. This helps reduce the number of http requests for the webpage. In genera

Re: container "accel"

Thanks! Any brief description (not detailed description, but from high level) about how content acceleration works in Shindig? Caching? Prefetch? Gerald On Wed, Oct 13, 2010 at 10:13 PM, Gagandeep singh wrote: > Hi Zhenhua > > Like John mentioned, accel container encompasses rewriters and servl

Re: container "accel"

Hi Zhenhua Like John mentioned, accel container encompasses rewriters and servlets that can be used to accelerate served content. Currently there are some optimizing rewriters like proxying embedded content through shindig host and more are on their way. Maybe once we have some more rewriters, we

Re: container "accel"

Not really, it's just a placeholder as far as its configuration is concerned. The new functionality is best understood through reading the code @ this point, since it's quite new. --j On Wed, Oct 13, 2010 at 5:47 PM, Zhenhua Guo wrote: > Thanks! > Any document for this new container? > > Gerald

Re: container "accel"

Thanks! Any document for this new container? Gerald On Wed, Oct 13, 2010 at 4:57 PM, John Hjelmstad wrote: > Accel is the container code used for the content acceleration code in > Shindig. > > On Wed, Oct 13, 2010 at 12:23 PM, Zhenhua Guo wrote: > >> I am upgrading from shindig 1.1 beta5 to sh

Re: container "accel"

Accel is the container code used for the content acceleration code in Shindig. On Wed, Oct 13, 2010 at 12:23 PM, Zhenhua Guo wrote: > I am upgrading from shindig 1.1 beta5 to shindig 2.0.0. I found in the > config file "WEB-INF/classes/containers/default/container.js", a new > container named "a

container "accel"

I am upgrading from shindig 1.1 beta5 to shindig 2.0.0. I found in the config file "WEB-INF/classes/containers/default/container.js", a new container named "accel" is added. I wonder what is the difference between accel and default container. Thanks! Gerald