You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@oodt.apache.org by "Chris A. Mattmann (JIRA)" <ji...@apache.org> on 2011/06/05 03:35:49 UTC

[jira] [Updated] (OODT-11) Separate CAS-Resource serialization layers from interface implementations

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

Chris A. Mattmann updated OODT-11:
----------------------------------

    Fix Version/s:     (was: 0.3)
                   0.4

> Separate CAS-Resource serialization layers from interface implementations
> -------------------------------------------------------------------------
>
>                 Key: OODT-11
>                 URL: https://issues.apache.org/jira/browse/OODT-11
>             Project: OODT
>          Issue Type: Improvement
>          Components: resource manager
>    Affects Versions: 0.1-incubating
>         Environment: none
>            Reporter: Brian Foster
>            Priority: Minor
>             Fix For: 0.4
>
>
> Examples: Monitor and JobQueue. Make them an upper layer wrapper.
> - job, node, etc... serialization should be controlled by Resource Manager itself, however, the underlying serialization techniques used should still be customizable (i.e. introduction of a serialization interface for each set of information desired to be serialized - similar to JobRepository)

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira