[
https://issues.apache.org/jira/browse/TS-2431?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yunkai Zhang updated TS-2431:
-----------------------------
Description:
I must say, sorry for my late. And now, I have finished the first version, the
migration of Taobao SPDY plugin to ATS core.
But seriously speaking, the migration to ATS core is finished *partially*. I
had tried to remove the dependency of *fetcher* library created by @Quehan and
create a specific VC for each http request in spdy sm, but I found it was too
difficult, so I give up temporarily.
Let me push this series patches to here before it's perfect enough, at least,
this series can statisfy TAOBAO's current demand (in fact, this version has had
good performance in our testing, but it can do much better I think).
I had thought another solution instread of recreating a new VC for each http
request in spdy sm, which will replace FetchSM's function and speed up SPDY
protocol, but will not change the framework of this version. So I can hacking
it based on these patches in the future.
==How to test it==
*) Need not to config anything.
The code can recognize SPDY or HTTP by reading this first bytes of request.
*) You can use *spdycat* in spdylay(or other SPDY client) to do request, for
example:
{code}
# Now, not supoort SSL in SPDY, we should use '--no-tls' option in spdycat
$ spdycat -3 -v --no-tls http://localhost/b.txt
{code}
*) You can enable debuging logs of SPDY:
{code}
CONFIG proxy.config.diags.debug.enabled INT 1
CONFIG proxy.config.diags.debug.tags STRING spdy
{code}
==TODO===
- Migrate spdy configuration to ATS records.config
- SSL + SPDY support, it should be easy, just like SSL + HTTP (I'll develop it
soon).
Any feedbacks are welcome.
was:
I must say, sorry for my late. And now, I have finished the first version, the
migration of Taobao SPDY plugin to ATS core.
But seriously speaking, the migration to ATS core is finished *partially*. I
had tried to remove the dependency of *fetcher* library created by @Quehan and
create a specific VC for each http request in spdy sm, but I found it was too
difficult, so I give up temporarily.
Let me push this series patches to here before it's perfect enough, at least,
this series can statisfy TAOBAO's current demand (in fact, this version has had
good performance in our testing, but it can do better I think).
I had thought another solution instread of recreating a new VC for each http
request in spdy sm, which will replace FetchSM's function and speed up SPDY
protocol, but will not change the framework of this version. So I can hacking
it based on these patches in the future.
==How to test it==
*) Need not to config anything.
The code can recognize SPDY or HTTP by reading this first bytes of request.
*) You can use spdycat to other SPDY client to do request, for example:
{code}
# Now, not supoort SSL in SPDY, we should use '--no-tls' option in spdycat
$ spdycat -3 -v --no-tls http://localhost/b.txt
{code}
*) You can enable debuging logs of SPDY:
{code}
CONFIG proxy.config.diags.debug.enabled INT 1
CONFIG proxy.config.diags.debug.tags STRING spdy
{code}
==TODO===
- Migrate spdy configuration to ATS records.config
- SSL + SPDY support, it should be easy, just like SSL + HTTP (I'll develop it
soon).
Any feedbacks are welcome.
> Add SPDY supporting to ATS
> --------------------------
>
> Key: TS-2431
> URL: https://issues.apache.org/jira/browse/TS-2431
> Project: Traffic Server
> Issue Type: New Feature
> Components: HTTP
> Reporter: Yunkai Zhang
> Assignee: Yunkai Zhang
> Fix For: 5.0.0
>
> Attachments: 0001-TS-2431-Preparation-of-SPDY-protocol.patch,
> 0002-TS-2431-Add-autoconf-options-for-SPDY.patch,
> 0003-TS-2431-Extends-and-optimizes-FetchSM.patch,
> 0004-TS-2431-Implement-dechunk-supporting-in-FetchSM.patch,
> 0005-TS-2431-Migrate-Taobao-SPDY-plugin-to-ATS-core.patch
>
>
> I must say, sorry for my late. And now, I have finished the first version,
> the migration of Taobao SPDY plugin to ATS core.
> But seriously speaking, the migration to ATS core is finished *partially*. I
> had tried to remove the dependency of *fetcher* library created by @Quehan
> and create a specific VC for each http request in spdy sm, but I found it was
> too difficult, so I give up temporarily.
> Let me push this series patches to here before it's perfect enough, at least,
> this series can statisfy TAOBAO's current demand (in fact, this version has
> had good performance in our testing, but it can do much better I think).
> I had thought another solution instread of recreating a new VC for each http
> request in spdy sm, which will replace FetchSM's function and speed up SPDY
> protocol, but will not change the framework of this version. So I can hacking
> it based on these patches in the future.
> ==How to test it==
> *) Need not to config anything.
> The code can recognize SPDY or HTTP by reading this first bytes of request.
> *) You can use *spdycat* in spdylay(or other SPDY client) to do request, for
> example:
> {code}
> # Now, not supoort SSL in SPDY, we should use '--no-tls' option in spdycat
> $ spdycat -3 -v --no-tls http://localhost/b.txt
> {code}
> *) You can enable debuging logs of SPDY:
> {code}
> CONFIG proxy.config.diags.debug.enabled INT 1
> CONFIG proxy.config.diags.debug.tags STRING spdy
> {code}
> ==TODO===
> - Migrate spdy configuration to ATS records.config
> - SSL + SPDY support, it should be easy, just like SSL + HTTP (I'll develop
> it soon).
> Any feedbacks are welcome.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
