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

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

                Author: ASF GitHub Bot
            Created on: 20/Sep/16 03:44
            Start Date: 20/Sep/16 03:44
    Worklog Time Spent: 10m 
      Work Description: Github user oknet commented on a diff in the pull 
request:

    https://github.com/apache/trafficserver/pull/753#discussion_r79531880
  
    --- Diff: iocore/net/UnixNetAccept.cc ---
    @@ -281,29 +280,30 @@ NetAccept::do_blocking_accept(EThread *t)
           return -1;
         }
     
    +    if (check_emergency_throttle(con)) {
    +      // `con' could be closed if there is hyper emergency
    +      if (con.fd == NO_FD) {
    +        return 0;
    +      }
    +    }
    +
    --- End diff --
    
    @jpeach , Here is a similar bug as PR #1033 


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

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

> Proposal: NetVC Context
> -----------------------
>
>                 Key: TS-4705
>                 URL: https://issues.apache.org/jira/browse/TS-4705
>             Project: Traffic Server
>          Issue Type: Improvement
>          Components: Core
>            Reporter: Oknet Xu
>            Assignee: Oknet Xu
>             Fix For: 7.1.0
>
>          Time Spent: 3h 10m
>  Remaining Estimate: 0h
>
> Goal 1st:
> In the NetVConnection, we have get_local_addr() and get_remote_addr() methods.
> Also have members local_addr, remote_addr and netvc->con.addr.
> Thus, we should using netvc->con.addr or remote_addr to replace member 
> server_addr in UnixNetVConnection.
> Goal 2nd:
> SSLNetVConnection has member sslClientConnection with 2 methods 
> setSSLClientConnection() and getSSLClientConnection() to indictor ATS is a 
> client or server in a SSL session.
> To abstract above two goals, I'm design the netvc context function.
> As a proxy, there has two side: client side ( Client <-> Proxy ) and server 
> side ( Proxy <-> Server ). With the netvc context funtion to indicate which 
> side the NetVC working on.
> Goal 3rd:
> Fix a minor bug in NetAccept::do_blocking_accept, call to 
> check_emergency_throttle(con) first then allocate vc.
> Goal 4th:
> NetAccept Optimize, remove dup code, etc...



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to