You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@thrift.apache.org by "Jens Geyer (Jira)" <ji...@apache.org> on 2024/09/02 22:27:00 UTC
[jira] [Updated] (THRIFT-5778) Machine readable way to describe client-side service bindings
[ https://issues.apache.org/jira/browse/THRIFT-5778?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jens Geyer updated THRIFT-5778:
-------------------------------
Component/s: Compiler (General)
> Machine readable way to describe client-side service bindings
> -------------------------------------------------------------
>
> Key: THRIFT-5778
> URL: https://issues.apache.org/jira/browse/THRIFT-5778
> Project: Thrift
> Issue Type: New Feature
> Components: Compiler (General)
> Reporter: Jens Geyer
> Priority: Major
> Time Spent: 1h 10m
> Remaining Estimate: 0h
>
> Describing the endpoint specifics for a Thrift API today is a purely text-adventure like exercise, which leaves the client end with the task to set up and stack together a proper protocol/transport stack. That sometimes even leads to headaches, e.g. if the server requires e.g. framed protocol which might not be obvious.
> The use of a generally accepted, machine-readable and extensible format to describe client bindings could streamline that process.
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)