[OODT-11] Separate CAS-Resource serialization layers from interface implementations

• Type: Improvement
• Status: Resolved
• Priority: Minor
• Resolution: Won't Fix
• Affects Version/s: 0.1-incubating
• Fix Version/s: 0.11
• Component/s: resource manager

Environment

none

• Assignee: Unassigned
• Reporter: Brian Foster
• Created: 11/Mar/10 17:21
• Updated: 30/Aug/15 21:41
• Resolved: 30/Aug/15 21:41

Description

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)