liche Nachricht-
From: James E. King III
Sent: Wednesday, May 22, 2019 10:54 PM
To: jle...@lightblue.com
Cc: James E. King III ; dev@thrift.apache.org ; Jens Geyer
Subject: Re: THRIFT-66 - Bidirectional communication
I think that given the conversation thus far, IDL changes to support
bidirectional
jk...@apache.org]
> Sent: 21 May 2019 15:17
> To: dev@thrift.apache.org; jle...@lightblue.com
> Cc: Jens Geyer
> Subject: Re: THRIFT-66 - Bidirectional communication
>
> I'd prefer to see a solution that implements bidirectional request/response
> over a single transpor
]
Sent: 21 May 2019 15:17
To: dev@thrift.apache.org; jle...@lightblue.com
Cc: Jens Geyer
Subject: Re: THRIFT-66 - Bidirectional communication
I'd prefer to see a solution that implements bidirectional request/response
over a single transport; the in/out stuff hasn't been requested bef
is, so only
> the extra plumbing language-specific code needs to written.
>
>
> -Original Message-
> From: Jens Geyer [mailto:je...@apache.org]
> Sent: 20 May 2019 21:53
> To: dev@thrift.apache.org
> Subject: Re: THRIFT-66 - Bidirectional communication
>
> Hi,
language-specific code needs to written.
-Original Message-
From: Jens Geyer [mailto:je...@apache.org]
Sent: 20 May 2019 21:53
To: dev@thrift.apache.org
Subject: Re: THRIFT-66 - Bidirectional communication
Hi,
Sorry, I can't follow. IDL generates language specific code already.
G
20, 2019 7:26 AM
To: dev@thrift.apache.org
Subject: RE: THRIFT-66 - Bidirectional communication
And the benefit would be ... ?
The ability to extend functionality across all languages in a consistent way
using the existing implementation.
The only additional language-specific code that wou
nal Message-
From: Jens Geyer [mailto:jensge...@hotmail.com]
Sent: 19 May 2019 21:01
To: dev@thrift.apache.org
Subject: Re: THRIFT-66 - Bidirectional communication
> > > async was already a keyword long ago. It's now called "oneway".
> But 'oneway' provides
> > What exactly would that preprocessor do? Generate IDL from IDL?
> Yes.
And the benefit would be ... ?
-Ursprüngliche Nachricht-
From: John Dougrez-Lewis
Sent: Saturday, May 18, 2019 8:39 AM
To: dev@thrift.apache.org
Subject: RE: THRIFT-66 - Bidirectional communication
Hi
parameter is always going to be possible with
every language. There may be some languages where basic types are
always passed by value and/or have no concept of references or
pointers. Those would not be able to handle "out" semantics.
- Jim
>
> -
>
> Reg
--
Regards,
John
-Original Message-
From: Jens Geyer [mailto:je...@apache.org]
Sent: 17 May 2019 23:36
To: dev@thrift.apache.org
Subject: Re: THRIFT-66 - Bidirectional communication
Hi,
> That gets you to the point where Thrift supports and generates
> bidirectional, async
3)
=>
A=>B
Handletype functionName (arg1, arg2, arg3in)
B=>A
void functionName (Handletype, returntype, arg3out)
-Original Message-
From: James E. King III [mailto:jk...@apache.org]
Sent: 15 May 2019 19:02
To: jle...@lightblue.com
Cc: James E. King III; dev@thrift.apache.org
Subject:
; void functionName (Handletype, returntype, arg3)
> >
> > ===
> >
> > 3)
> >
> > A<=>B
> >
> > [async] returntype functionName (arg1, arg2, [inout] arg3)
> >
> > >
> >
> > A=>B
> >
> &g
=
>
> 3)
>
> A<=>B
>
> [async] returntype functionName (arg1, arg2, [inout] arg3)
>
> >
>
> A=>B
>
> Handletype functionName (arg1, arg2, arg3in)
>
> B=>A
>
> void functionName (Handletype, returntype, arg3out)
>
nout] arg3) => A=>B
Handletype functionName (arg1, arg2, arg3in) B=>A
void functionName (Handletype, returntype, arg3out)
-Original Message-
From: James E. King III [mailto:jk...@apache.org]
Sent: 15 May 2019 19:02
To: jle...@lightblue.com
Cc: James E. King III; dev@thrift.apac
rg3in)
B=>A
void functionName (Handletype, returntype, arg3out)
-Original Message-
From: James E. King III [mailto:jk...@apache.org]
Sent: 15 May 2019 19:02
To: jle...@lightblue.com
Cc: James E. King III; dev@thrift.apache.org
Subject: Re: THRIFT-66 - Bidirectional communication
Re:
and extended
> version of the IDL.
>
> Regards,
>
> John
>
> -Original Message-
> From: James E. King III [mailto:jk...@apache.org]
> Sent: 15 May 2019 12:05
> To: dev@thrift.apache.org; jle...@lightblue.com
> Subject: Re: THRIFT-66 - Bidirectional communica
htblue.com
Subject: Re: THRIFT-66 - Bidirectional communication
Hello!
Thrift is still a dedicated client/server model environment where clients can
request and servers reply. The easiest way to make it 2-way today is to open a
connection both ways. If you don't have firewalls in the way then y
Hello!
Thrift is still a dedicated client/server model environment where
clients can request and servers reply. The easiest way to make it
2-way today is to open a connection both ways. If you don't have
firewalls in the way then you can do this effectively. The more
difficult and more correct
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'
19 matches
Mail list logo
