thrift-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jens Geyer (Jira)" <>
Subject [jira] [Assigned] (THRIFT-4919) THttpTransport.cs (netstd) and THttpClientTransport (netcore) have bad timeout code
Date Mon, 19 Aug 2019 21:44:00 GMT


Jens Geyer reassigned THRIFT-4919:

    Assignee: Jens Geyer

> THttpTransport.cs (netstd) and THttpClientTransport (netcore) have bad timeout code
> -----------------------------------------------------------------------------------
>                 Key: THRIFT-4919
>                 URL:
>             Project: Thrift
>          Issue Type: Bug
>    Affects Versions: 0.12.0
>            Reporter: Al Tam
>            Assignee: Jens Geyer
>            Priority: Critical
> THttpTransport.cs (netstd) and THttpClientTransport (netcore) have the same identical
and badly written timeout configuration code.
>  # the code is using Timespan.FromSeconds(), yet the coder wants the variable to be using
>  # the timeout is permanently set to the class initialized value since the timeout is
only used within constructor, rendering the property useless
> Incidentally, there's no way to configure timeout except for using reflection.
> Also, if the ConnectTimeout property is NOT readable, how can people determine what's
used for the timeout?  It should be readable too.

This message was sent by Atlassian Jira

View raw message