[ 
https://issues.apache.org/jira/browse/TS-4882?focusedWorklogId=29574&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-29574
 ]

ASF GitHub Bot logged work on TS-4882:
--------------------------------------

                Author: ASF GitHub Bot
            Created on: 23/Sep/16 02:30
            Start Date: 23/Sep/16 02:30
    Worklog Time Spent: 10m 
      Work Description: Github user SolidWallOfCode commented on a diff in the 
pull request:

    https://github.com/apache/trafficserver/pull/1036#discussion_r80172843
  
    --- Diff: iocore/net/Net.cc ---
    @@ -56,82 +57,58 @@ configure_net(void)
     static inline void
     register_net_stats()
     {
    -  //
    -  // Register statistics
    -  //
    -  RecRegisterRawStat(net_rsb, RECT_PROCESS, 
"proxy.process.net.net_handler_run", RECD_INT, RECP_PERSISTENT,
    -                     (int)net_handler_run_stat, RecRawStatSyncSum);
    -  NET_CLEAR_DYN_STAT(net_handler_run_stat);
    -
    -  RecRegisterRawStat(net_rsb, RECT_PROCESS, 
"proxy.process.net.read_bytes", RECD_INT, RECP_PERSISTENT, 
(int)net_read_bytes_stat,
    -                     RecRawStatSyncSum);
    +  using std::make_pair;
    --- End diff --
    
    Why this `using`?


Issue Time Tracking
-------------------

    Worklog Id:     (was: 29574)
    Time Spent: 3h 20m  (was: 3h 10m)

> 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: 3h 20m
>  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
(v6.3.4#6332)

Reply via email to