[
https://issues.apache.org/jira/browse/THRIFT-5778?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jens Geyer updated THRIFT-5778:
-------------------------------
Description:
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.
was:
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 Thrift URI format to describe client bindings could streamline that
process.
Details (work in progress) at
https://github.com/Jens-G/thrift/blob/thrift-uri/doc/specs/thrift-uri.md
> 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
> 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)
