[
http://opencast.jira.com/browse/MH-9418?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=32956#comment-32956
]
Jaime Gago commented on MH-9418:
--------------------------------
It is indeed a lot of work in terms of code modification but it also means IMHO
some design thinking, as you point out maybe he workflow ID is the one to be
passed all along, also how far is it possible to take this concept? Can the UID
be found in error stack traces as well? How is this UID being glued when
Matterhorn "shells out" for example for ffmpeg or mediainfo commands?
I don't think this can make it in 1.4 but I certainly hope we can have such
"sticky" UID implemented somewhere in 1.4.x
> As a Matterhorn Systems Administrator I want to be able to track events
> lifecycle in the logs through their UIDs
> ----------------------------------------------------------------------------------------------------------------
>
> Key: MH-9418
> URL: http://opencast.jira.com/browse/MH-9418
> Project: Matterhorn Project
> Issue Type: Story Card
> Components: Administrative Tools
> Reporter: Jeff Austin
>
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
http://opencast.jira.com/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________
Matterhorn mailing list
[email protected]
http://lists.opencastproject.org/mailman/listinfo/matterhorn
To unsubscribe please email
[email protected]
_______________________________________________
