RE: THRIFT-66 - Bidirectional communication

2019-05-21 Thread John Dougrez-Lewis
e transport far outweighs additional code generation to glue two transports together. On Tue, May 21, 2019 at 1:22 AM John Dougrez-Lewis wrote: > > Indeed, you could just skip the intermediate IDL generation and go straight > to the language-specific code generation. > > T

RE: THRIFT-66 - Bidirectional communication

2019-05-20 Thread John Dougrez-Lewis
eat, simple and "to the point" IDL we have aleady, maybe expand it a bit where suche becomes necessary? Have fun, JensG -Ursprüngliche Nachricht- From: John Dougrez-Lewis Sent: Monday, May 20, 2019 7:26 AM To: dev@thrift.apache.org Subject: RE: THRIFT-66 - Bidirectional communi

RE: THRIFT-66 - Bidirectional communication

2019-05-19 Thread John Dougrez-Lewis
no guaranteed deterministic mechanism of > indicating back to the client any I didn't say that. I just said that async already was used as a keyword. > > What exactly would that preprocessor do? Generate IDL from IDL? > Yes. And the benefit would be ... ? -Ursprüngliche Na

RE: THRIFT-66 - Bidirectional communication

2019-05-17 Thread John Dougrez-Lewis
ata are transferred in a struct anyway, so multiple out parameters (or even in/out) should really not be that hard to implement. I have no idea if we run into subtle problems with certain languages and how that could be circumvented (by using structs maybe) and if in/out is really supported by all

RE: THRIFT-66 - Bidirectional communication

2019-05-15 Thread John Dougrez-Lewis
nctionName (arg1, arg2, [inout] arg3) > A=>B Handletype functionName (arg1, arg2, arg3in) B=>A void functionName (Handletype, returntype, arg3out) -Original Message- From: John Dougrez-Lewis [mailto:jle...@lightblue.com] Sent: 16 May 2019 05:29 To: James E. King III Cc:

RE: THRIFT-66 - Bidirectional communication

2019-05-15 Thread John Dougrez-Lewis
Thrift cannot do the latter today, so I would recommend the former, using one transport for each direction. Given they will both be on the same system, if your languages support it, unix domain sockets are quite fast. Otherwise if you want a shared memory solution you need to write your own

RE: THRIFT-66 - Bidirectional communication

2019-05-15 Thread John Dougrez-Lewis
r things like reliable delivery and broadcast semantics but that also does not exist today. - Jim On Wed, May 15, 2019 at 1:05 AM John Dougrez-Lewis wrote: > > Hi, > > > > I was looking for a mechanism to be able to provide language-agnostic > API support to a hobby project

THRIFT-66 - Bidirectional communication

2019-05-14 Thread John Dougrez-Lewis
Hi, I was looking for a mechanism to be able to provide language-agnostic API support to a hobby project I've been working on for some time. By following a trail of papers, books and references, I eventually came across Apache Thrift and have found and started going through Randy Abernethy'