[
https://issues.jboss.org/browse/SRAMP-433?page=com.atlassian.jira.plugin....
]
Gary Brown commented on SRAMP-433:
----------------------------------
I don't think the client should have any control - it should just be a recipient of
events. SRAMP should just be configured with the relevant destinations without caring if
there is a recipient - so truly decoupled.
So its the choice of the event producer (i.e. jms queue or durable topic) that dictates
the quality of service (i.e. guaranteed delivery or fire and forget).
I think the format of events may not always be in our control, so we probably
shouldn't fix the format - however we would hope that generally it will be xml or
json. Would prefer not to deal with serialized java objects, although it would not
necessarily be a show stopper.
Perhaps for sramp we should just use something simple - e.g. json, and define our own
format for use in cases where we do control the publisher.
Create a proper Event producer for s-ramp
-----------------------------------------
Key: SRAMP-433
URL:
https://issues.jboss.org/browse/SRAMP-433
Project: S-RAMP
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: Core
Reporter: Eric Wittmann
Assignee: Brett Meyer
Fix For: 0.6.0
Currently dtgov monitors s-ramp for changes by polling. It would be more efficient if
dtgov could listen for events it cared about.
Ideally we could add a listener to the s-ramp repository either at the global level or by
including a filter of some kind, so we can make sure to get only a subset of the total
events coming from the server.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)