Revert "feat(module): new method peer_conn.get_last_peer_connection_cached (#82)"

This reverts commit d1f8aaf.

Signed-off-by: tzssangglass <[email protected]>

Author: tzssangglass

README.md

@@ -30,9 +30,7 @@ Table of Contents
     * [resty.kong.tag.get](#restykongtagget)
     * [resty.kong.log.set\_log\_level](#restykonglogset_log_level)
     * [resty.kong.log.get\_log\_level](#restykonglogget_log_level)
-    * [resty.kong.peer_conn.get\_last\_peer\_connection\_cached](#restykongpeer_connget_last_peer_connection_cached)
     * [resty.kong.upstream.set\_next\_upstream](#restykongupstreamset_next_upstream)
-
 * [License](#license)
 
 Description
@@ -526,59 +524,6 @@ for the possible value of `level`.
 
 [Back to TOC](#table-of-contents)
 
-resty.kong.peer_conn.get\_last\_peer\_connection\_cached
-----------------------------------
-**syntax:** *res = resty.kong.peer_conn.get_last_peer_connection_cached()*
-
-**context:** *balancer_by_lua*
-
-**subsystems:** *http*
-
-This function retrieves information about whether the connection used in the previous attempt came from the upstream connection pool when the next_upstream retrying mechanism is in action.
-
-The possible results are as follows:
-- `false`: Indicates the connection was not reused from the upstream connection pool, meaning a new connection was created with the upstream in the previous attempt.
-- `true`: Indicates the connection was reused from the upstream connection pool, meaning no new connection was created with the upstream in the previous attempt.
-
-After applying the [dynamic upstream keepalive patch](https://github.com/Kong/kong/blob/3.6.0/build/openresty/patches/ngx_lua-0.10.26_01-dyn_upstream_keepalive.patch),
-Nginx's upstream module attempts to retrieve connections from the upstream connection pool for each retry.
-If the obtained connection is deemed unusable, Nginx considers that retry invalid and performs a compensatory retry.
-
-Since each retry triggers the `balancer_by_lua` phase, the number of retries logged in Lua land during this phase may exceed the maximum limit set by `set_more_tries`.
-
-Using this function in the `balancer_by_lua` phase allows for determining if the connection used in the previous retry was taken from the connection pool.
-If the return value is `true`, it indicates that the connection from the pool used in the previous retry was unusable, rendering that retry void.
-
-The value returned by this function helps in accurately assessing the actual number of new connections established with the upstream server during the retry process during the `balancer_by_lua phase`.
-
-Example:
-```lua
-balancer_by_lua_block {
-    local ctx = ngx.ctx
-
-    ctx.tries = ctx.tries or {}
-    local tries = ctx.tries
-
-    -- update the number of tries
-    local try_count = #tries + 1
-
-    -- fetch the last peer connection cached
-    local peer_conn = require("resty.kong.peer_conn")
-    local last_peer_connection_cached = peer_conn.get_last_peer_connection_cached()
-    if try_count > 1 then
-        local previous_try = tries[try_count - 1]
-        previous_try.cached = peer_conn.get_last_peer_connection_cached()
-    else
-        tries[try_count].cached = false
-    end
-    
-    ...
-}
-```
-
-[Back to TOC](#table-of-contents)
-
-
 resty.kong.upstream.set\_next\_upstream
 ----------------------------------
 **syntax:** *res = resty.kong.upstream.set_next_upstream("http_404")*
@@ -614,7 +559,6 @@ previous ones.
 [Back to TOC](#table-of-contents)
 
 
-
 License
 =======
 

config

@@ -9,7 +9,6 @@ ngx_module_srcs=" \
                 $ngx_addon_dir/src/ngx_http_lua_kong_log.c \
                 $ngx_addon_dir/src/ngx_http_lua_kong_log_handler.c \
                 $ngx_addon_dir/src/ngx_http_lua_kong_vars.c \
-                $ngx_addon_dir/src/ngx_http_lua_kong_peer_connection.c \
                 $ngx_addon_dir/src/ssl/ngx_lua_kong_ssl.c \
                 "