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
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
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
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
Thanks!
Any document for this new container?
Gerald
On Wed, Oct 13, 2010 at 4:57 PM, John Hjelmstad fa...@google.com 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 jen...@gmail.com wrote:
I am upgrading
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 jen...@gmail.com wrote:
Thanks!
Any document for this new
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,
