[
https://issues.jboss.org/browse/RTGOV-328?page=com.atlassian.jira.plugin....
]
Jiri Pechanec reopened RTGOV-328:
---------------------------------
The reason is pretty simple - I believe that activity collection should have as least
impact as possible on the client system. If we delegate the async processing on the server
then it is fire-and-forget on the side on client with a minimum performance impact. If we
keep it on client then some of the CPU cycles of the monitored system will be spent on
activity processing.
Activity Server should support async processing of submitted events
-------------------------------------------------------------------
Key: RTGOV-328
URL:
https://issues.jboss.org/browse/RTGOV-328
Project: RTGov (Run Time Governance)
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: Activity Server
Affects Versions: 1.0.0.Final
Reporter: Jiri Pechanec
Assignee: Gary Brown
Fix For: 2.1.0.Final
Activity Collector does not care about return value from activity server invocation. Thus
the api should provide a method that will allow submit activities in one-way fashion. The
REST invocation will return immediately and the activities will be stored in storage
asynchronously in another thread.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)