我试图对玉米申请进行规划,以便询问一个高性能计算组,了解其运作和轮值计算工作。 目的是能够监测已提交的工作,如果这些职位仍然被解雇和等待处决,或者如果他们正在经营,并且是该组群的 no或主人。
在“全球倡议”方面,我希望能够展示一个<条码>可衡量的<>条码>,其中显示所有已提交的工作,另外还有第二个选择,即看到该组的所有东道方,以及每个节点有多少和哪些工作正在进行。
模型本身并不难做,我最大的是生命周期和东道方与工作对象之间的所有权关系。 这必须设计得好,否则,我将面临记忆管理问题。
www.un.org/Depts/DGACM/index_spanish.htm 请注意,如果可能的话,我想不使用核心数据。
1. Possibility
The yellow queue object is the root object of my object graph and it owns all the host objects (has an NSArray of custom host objects). Each host object owns all the job object which are running on this host (also by having an NSArray of custom job objects). I think that there are two major problems with this approach:
- where are all the job objects store which are still queued and are not already running on a host. They lack a parent host object.
- How would one implement a
NSTableViewcontaining all the job objects?
2. Possibility
The yellow root object holds directly references to all job objects by having them stored in a NSArray. Each job has an instance variable retaining a host object. Again here are some problems
- I would also have the hosts in the model which are currently idle, so no job is currently executed on them.
- How would one implement the data source for a
NSTableViewshowing all the hosts. - How does one make sure that there are no duplicate host objects, so that each host in the cluster is represented by one host object only.
My questions are: 1. Which of the two possibilities make most sense? Are there alternatives? 2. Would one better implement it with CoreData? 3. How would one manage the object lifecycle so that there are no retain cycles or dangling pointers.
www.un.org/Depts/DGACM/index_spanish.htm 谢谢<>。