Andre, Some comments on get_self() below. Graeme Andre Merzky wrote:
Quoting [Graeme Pound] (Mar 03 2006): [...]
-3.37 I do not understand the purpose of job_service.get_self() which returns a Job object.
Use case is the following (pseudo code-ish:
main () { saga::job_service js ("xyz"); saga::job me = js.get_self ();
saga::job_status s = me.get_status (); // should be running ;-)
// start to do some work
// after a while, do something to MY instance me.migrate ("some new big resource");
return (0); }
Basically, the job returned represents the application calling get_self, and allows to perform actions on that application (like suspending myself via the resource manager).
Should make that more clear in the spec I guess... ;-)
I am afraid that I find this a little bizarre. As I understand it; job_service.get_self() returns a representation of the _local_ client application which has instantiated the job_service object (is that correct?). This would allow the client application to perform operations upon itself via the 'job' interface. This raises several questions (how and why), but I am unsure if my understanding is correct.