I appreciate that, Sijie, but in practise I think the tooling would collide.
I am most productive in Scala and akka-http, and I think those are a good platform for the future. Doing something HTTP and Websocket based in Java is outside of my experience, and willingness. While merging the two together is practically possible (both are on JVM) I don’t really see the point. But anyways, the low hanging fruit is planning the interface and I already did some drafts on that, as a discussion starter with Jay. Asko Kauppi Zalando Tech Helsinki > On 22 Dec 2016, at 21.43, Sijie Guo <si...@apache.org> wrote: > > One thought about the REST/websockets proxy - it would be good that it can > be part of current proxy (so people doesn't have to deploy additional > services) or another module for this project **eventually**. You can choose > the best way for you guys to collaborate on the development. If you guys > are willing to instantiate this within this project, a new module might be > a good starting point.
