You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@uima.apache.org by "Jerry Cwiklik (JIRA)" <de...@uima.apache.org> on 2017/07/19 17:21:00 UTC

[jira] [Updated] (UIMA-5280) UIMA-AS V3: Redesign to simplify embedding in applications

     [ https://issues.apache.org/jira/browse/UIMA-5280?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jerry Cwiklik updated UIMA-5280:
--------------------------------
    Summary: UIMA-AS V3: Redesign to simplify embedding in applications  (was: Redesign UIMA-AS to simplify embedding in applications)

> UIMA-AS V3: Redesign to simplify embedding in applications
> ----------------------------------------------------------
>
>                 Key: UIMA-5280
>                 URL: https://issues.apache.org/jira/browse/UIMA-5280
>             Project: UIMA
>          Issue Type: Improvement
>          Components: Async Scaleout
>            Reporter: Jerry Cwiklik
>            Assignee: Jerry Cwiklik
>             Fix For: 3.0.0AS
>
>
> The current UIMA-AS runtime requires an ActiveMQ broker to be running to support message exchanges between an application and UIMA-AS based service. An application uses the UIMA-AS client API to send CASes to a service for analysis. A CAS is serialized by the client, wrapped in a Message object and delivered to a JMS queue. A service than dequeues the message and deserializes a CAS contained within it. Reverse happens on a reply. In total, such exchange requires two serializations and two deserializations of the CAS.
> To avoid such overhead, a collocated service deployment in the new design will use java queues for transport and pass a CAS by reference.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)