[jira] [Work logged] (TS-4705) Proposal: NetVC Context

["ASF GitHub Bot (JIRA)" <ji...@apache.org>]

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

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

                Author: ASF GitHub Bot
            Created on: 12/Aug/16 16:02
            Start Date: 12/Aug/16 16:02
    Worklog Time Spent: 10m 
      Work Description: Github user shinrich commented on the issue:

    https://github.com/apache/trafficserver/pull/753
  
    Looks good to me!


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

    Worklog Id:     (was: 26357)
    Time Spent: 40m  (was: 0.5h)

> 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.0.0
>
>          Time Spent: 40m
>  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)