On 12. Dec 2022, at 17:20, Eddie Epstein <eaepst...@gmail.com> wrote: > > The combination of uimacpp + amq-cpp does support non-JNI interoperability > with uimaj. Although I am only familiar with using uimacpp as a remote > component for uimaj applications, it may not be hard for uimacpp to be an > application that uses uimaj remote annotators. It is not clear to me that > such CAS interface connectivity would be more useful than standard > messaging interfaces from python to a java-based process. > > What scenarios do you have in mind?
Setting up a message queueing system is extra overhead. It is certainly the more scalable solution, but it is not at the level of convenience of "pip install" or adding a Maven dependency. Personally, I had mostly the issue of being able to call Python DL frameworks from Java. For my purposes at the moment, wrapping deploying the Python stuff in a Docker container and exposing it as a HTTP (micro)service using CAS XMI or CAS JSON as the wire protocol does the trick. Not very efficient but otherwise a good balance between effort and effect. But I'd be interested in the use-cases that others have. The questions from my last mail were meant as potential hooks that others could use to bring up their scenarios as well. That said, I think we lost some people on the way because UIMA didn't have a good answer when the Python wave rolled in. When people ask me today, I point them to Cassis which addresses those parts that pained me most (e.g. I use it in those Docker containers mentioned above). But again, my perspective is only one of many and I would be interested in hearing other's views. Cheers, -- Richard
