Hey Anthony, your last comment seems to indicate that you disagree with tomcat being fixed requirement. Personally I feel opening a port and implementing all the protocol handling completely negates of advantages of having tomcat in your application. So maybe you should force a change in your requirements instead of undermining them, if you feel they are nonsense.
That being said, if you need a binary protocol on top of http you might want to check grpc. I am not sure how well it works with tomcat, there might be issues, since they use netty for default. The advantage of grpc would be multi-language support, http2 features, and the convenience that no-one ever got fired for using google technology. regards Leon On Sat, Sep 22, 2018 at 2:49 AM anthony berglas <anth...@berglas.org> wrote: > We would like to run a binary protocol in a Tomcat container, so that > binary sent to a specific port all ends up in a specific servlet. This is > not AJP, we do not want Tomcat itself to look at the bits, just pass them > through. > > So in Tomcat parlance we need a special Connector. > > Does such a thing exist or do we need to write it ourselves? > > Tomcat itself is a fixed requirement for the container architecture. Just > having a process listening on a port is not considered to be enterprisy > enough. > > Thanks, > > Anthony > > -- > > Dr Anthony Berglas, anth...@berglas.org Mobile: +61 4 4838 8874 > Just because it is possible to push twigs along the ground with ones nose > does not necessarily mean that that is the best way to collect firewood. >
