Asko, That's something that I am also looking for. I am interested in that.
One comment about "a REST / websockets proxy", are you thinking of running a separate service or part of current proxy (e.g. listening on a separate port to handle REST/websockets request)? - Jay On Wed, Dec 21, 2016 at 7:40 PM, Asko Kauppi <asko.kau...@zalando.fi> wrote: > Thanks for clarification. The question was not meant as criticism, just > trying to understand the architecture. > > Once/if we make a REST API / websockets proxy (of the current proxy), it > could also take care of access control? I’m thinking of a system where > access to data is close to the data, not at the services handling the data. > > Anyone interested in working on something like that? > > Asko Kauppi > Zalando Tech Helsinki > > > > On 21 Dec 2016, at 19.09, Leigh Stewart <lstew...@twitter.com.INVALID> > wrote: > > > > The challenge is the protocol uses a redirection mechanism so theres a > > protocol beyond thrift/transport. > > > > As Jay says we plan to make improvements in this area. > > > > On Wed, Dec 21, 2016 at 8:53 AM, Jay Juma <jayk.j...@gmail.com> wrote: > > > >> Hi Asko, > >> > >> I don't think there is a REST api available in the proxy service. The > API > >> seems to be thrift-rpc based. I found there is a JIRA to support gPRC > wire > >> protocol. It should not be difficult to add a REST api. > >> > >> - Jay > >> > >> On Wed, Dec 21, 2016 at 4:29 AM, Asko Kauppi <asko.kau...@zalando.fi> > >> wrote: > >> > >>> I’m reading http://distributedlog.incubator.apache.org/docs/ > >>> latest/user_guide/api/proxy.html <http://distributedlog. > >>> incubator.apache.org/docs/latest/user_guide/api/proxy.html> > >>> > >>> Ideally, I wouldn’t need to use a library to talk to a proxy service, > >>> right? Is there documentation on how to access the proxies as REST > >>> endpoints / are they such? > >>> > >>> My preferred environment is Scala and akka-http. > >>> > >>> Asko Kauppi > >>> Zalando Tech Helsinki > >>> > >>> > >> > >
