Return-Path: X-Original-To: apmail-trafficserver-users-archive@www.apache.org Delivered-To: apmail-trafficserver-users-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id AA14117DF3 for ; Tue, 28 Oct 2014 17:25:18 +0000 (UTC) Received: (qmail 22917 invoked by uid 500); 28 Oct 2014 17:25:18 -0000 Delivered-To: apmail-trafficserver-users-archive@trafficserver.apache.org Received: (qmail 22856 invoked by uid 500); 28 Oct 2014 17:25:18 -0000 Mailing-List: contact users-help@trafficserver.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: users@trafficserver.apache.org Delivered-To: mailing list users@trafficserver.apache.org Received: (qmail 22846 invoked by uid 99); 28 Oct 2014 17:25:18 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 28 Oct 2014 17:25:18 +0000 X-ASF-Spam-Status: No, hits=1.7 required=5.0 tests=FREEMAIL_ENVFROM_END_DIGIT,HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of jacksontj.89@gmail.com designates 209.85.212.182 as permitted sender) Received: from [209.85.212.182] (HELO mail-wi0-f182.google.com) (209.85.212.182) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 28 Oct 2014 17:25:14 +0000 Received: by mail-wi0-f182.google.com with SMTP id d1so2324864wiv.9 for ; Tue, 28 Oct 2014 10:22:38 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=YHQZSc7+Q51/yQWfJF0FBmJQE7TuWLzbhZk+n6+8AYE=; b=UnPSjd/yBexuBTBnvJc6rIaveXs/oPUqJtBvFtH+yyNOgDm4SjDMwQAUC+GtUAlB+f zWE70849xJXvcNYkE5XWA2Qzghg50Ccc7pdha5xLEDwRHq2kE81NJjyOr0u/4rJiv+7g r126UQn7tySrYSPk1UAoS1QBhVo8gRaxVeyqe+O/6Kpz7cqn1Wzb+C4ufHcGRYaemBMl BPAtBVoLZJFqEO1P72fMEzF44RTcviGoTRYxqx0dV8ZpbWDNzp4V0HKnR67Hj+oFnWFv jWuEoUiSCVIBz3Gwpu/40lEDPLbzwcXlT53GQwK/ti0Wq06reB5Wibol5+zE/8LhzW3g rKzw== MIME-Version: 1.0 X-Received: by 10.180.187.66 with SMTP id fq2mr6541382wic.58.1414516958052; Tue, 28 Oct 2014 10:22:38 -0700 (PDT) Received: by 10.216.36.69 with HTTP; Tue, 28 Oct 2014 10:22:37 -0700 (PDT) In-Reply-To: References: Date: Tue, 28 Oct 2014 10:22:37 -0700 Message-ID: Subject: Re: ats_pagespeed & spdy use case. From: Thomas Jackson To: "users@trafficserver.apache.org" Content-Type: multipart/alternative; boundary=001a11c262b4d046bc05067ee48d X-Virus-Checked: Checked by ClamAV on apache.org --001a11c262b4d046bc05067ee48d Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable It depends on how transparent you want your proxy to be really. SPDY will just change the transport between the client and the proxy, whereas pagespeed will change the actual content sent back to the client. On Tue, Oct 28, 2014 at 8:16 AM, Sudheer Vinukonda wrote: > SPDY is a part of the ATS core in 5.0+ (however, it needs to be built > explicitly with the option =C2=B3=E2=80=B9enable-spdy=C2=B2). > > The key benefit of the SPDY protocol is the support for multiplexing of > requests, thereby allowing for faster web page load. The > concurrency/multiplexing benefits should apply for a forward proxy > configuration as well. > > I=C2=B9ve not used ats_pagespeed plugin yet, but, reading the description= about > what it does at http://www.atspagespeed.com/ (to basically modify the > order of loading various types of resources on a web page to achieve > optimal page load latencies), it seems that, ats_pagespeed should also > help a forward proxy setup as well. > > > Thanks, > > Sudheer > > > > On 10/28/14, 4:20 AM, "Mohd Akhbar" wrote: > > >Hi, > > > >Is these 2 plugins really use for reverse proxy only ? Any benefit in > >forward proxy ? If i am wrong, can I have a simple explanation on > >these ? I'm building ATS on centos 6 and now 7 and all seem working. > >If these 2 plugins have any benefit for forward proxying then i'm > >happy to try and post some results here. > > > >Thank you. > > --001a11c262b4d046bc05067ee48d Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
It depends on how transparent you want your proxy to be re= ally. SPDY will just change the transport between the client and the proxy,= whereas pagespeed will change the actual content sent back to the client.<= div>



On Tue, Oct 28, 2014 at 8:16 AM, Sudheer V= inukonda <sudheerv@yahoo-inc.com> wrote:
SPDY is a part of the ATS core in 5.0+ (however, it nee= ds to be built
explicitly with the option =C2=B3=E2=80=B9enable-spdy=C2=B2).

The key benefit of the SPDY protocol is the support for multiplexing of
requests, thereby allowing for faster web page load. The
concurrency/multiplexing benefits should apply for a forward proxy
configuration as well.

I=C2=B9ve not used ats_pagespeed plugin yet, but, reading the description a= bout
what it does at = http://www.atspagespeed.com/ (to basically modify the
order of loading various types of resources on a web page to achieve
optimal page load latencies), it seems that, ats_pagespeed should also
help a forward proxy setup as well.


Thanks,

Sudheer



On 10/28/14, 4:20 AM, "Mohd Akhbar" <mymohaja@gmail.com> wrote:

>Hi,
>
>Is these 2 plugins really use for reverse proxy only ? Any benefit in >forward proxy ? If i am wrong, can I have a simple explanation on
>these ? I'm building ATS on centos 6 and now 7 and all seem working= .
>If these 2 plugins have any benefit for forward proxying then i'm >happy to try and post some results here.
>
>Thank you.


--001a11c262b4d046bc05067ee48d--