ASF GitHub Bot logged work on TS-4882:

                Author: ASF GitHub Bot
            Created on: 20/Sep/16 23:47
            Start Date: 20/Sep/16 23:47
    Worklog Time Spent: 10m 
      Work Description: GitHub user jpeach opened a pull request:


    [WIP] TS-4882: TCP Fast Open support for server sessions.


You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/jpeach/trafficserver fix/4882

Alternatively you can review and apply these changes as the patch at:


To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #1036
commit 9499442244d2028369b9202d66bbb227f64e1b5e
Author: James Peach <jpe...@apache.org>
Date:   2016-09-20T17:17:45Z

    TS-4882: Add a socket BIO for TCP Fast Open.

commit efe8521bd41825838ad33e22b4ef0b6520725cb5
Author: James Peach <jpe...@apache.org>
Date:   2016-09-20T18:44:37Z

    TS-4882: Implement TCP Fast Open for SSL.
    Wire up socket flag configuration for TCP Fast Open to be used on
    outbound SSL connections.

commit 8fca803cade9f2cc7ea4d8a855ef6b6df2d90a1d
Author: James Peach <jpe...@apache.org>
Date:   2016-09-20T22:49:24Z

    TS-4882: Implement TCP Fast Open for CONNECT tunnels.


Issue Time Tracking

            Worklog Id:     (was: 29417)
            Time Spent: 10m
    Remaining Estimate: 0h

> TCP Fast Open support for SSL server sessions.
> ----------------------------------------------
>                 Key: TS-4882
>                 URL: https://issues.apache.org/jira/browse/TS-4882
>             Project: Traffic Server
>          Issue Type: Improvement
>          Components: Core, SSL
>            Reporter: James Peach
>            Assignee: James Peach
>             Fix For: 7.1.0
>          Time Spent: 10m
>  Remaining Estimate: 0h
> Add support for using TCP Fast Open on TLS server sessions. This is mainly 
> interesting for CONNECT tunnels where we can't use long running persistent 
> sessions.

This message was sent by Atlassian JIRA

Reply via email to