Hi all,

We have identified that the events in the doc attached herewith are the
events which are triggered within each page. While some of them are already
published, some of them needs to be published to the social component in
order to enhance the user experience and collaboration. While doing this we
have encountered some issues and some resolutions are proposed to overcome
those issues.

*Problem*: There is no way to track whether a certain build or a deployment
instance triggered by someone is completed.(No association between start
and finish events for a certain instance). There is no way to represent an
ongoing process. (e.g. application creation in progress, build is in
progress etc.)

The same problem would be applied to any scenario where it takes some time
for a certain event to finish and app factory needs to capture both start
and completion events related to a particular instance.

*Solution* : Use a UUID to track events which takes time to complete

Publishing both start and complete events with the same UUID as a event
property would solve the problem. Then by looking at the event content we
are able to find whether there is a completion event for a certain start
event. This would be a global thing so the notification wall logic can be
written in such a manner that we need to have a look at only the UUID. If
we use different mechanisms for tracking start and completion events of
different events the notification wall logic would be more complex when
filtering out the events

Your thoughts are welcome.

[1] https://redmine.wso2.com/issues/3065

Thanks
GayanD

-- 
Gayan Dhanuska
Software Engineer
http://wso2.com/
Lean Enterprise Middleware

Mobile
071 666 2327

Office
Tel   : 94 11 214 5345
Fax  : 94 11 214 5300

Twitter : https://twitter.com/gayanlggd

Attachment: Events to be published to App Factory wall.ods
Description: application/vnd.oasis.opendocument.spreadsheet

_______________________________________________
Architecture mailing list
[email protected]
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture

Reply via email to