| Home | Trees | Indices | Help |
|
|---|
|
|
Client side view of a service.
Inherit from here when creating new service types.
| Instance Methods | |||
|
|||
|
|||
|
|||
|
|||
|
|||
|
|||
|
|||
|
Inherited from Inherited from |
|||
| Properties | |
|
Inherited from |
| Method Details |
Return a list of the jobs on the service which the user can access. This list will include all jobs owned by the user on the remote service that have not yet been archived or deleted. Use a filter to select jobs of a particular type.
|
Add a new request to the job queue. Messages from the job are sent to monitor. Returns the job id for the request, which is unique to the queue.
|
Grab a copy of the named job from the server. This should include enough information to reconstruct the job request. |
Send a control message to the job. Message should be pickleable. The structure of the message is specific to the type of job. Messages will be queued in the job control queue on the service until the job is ready to process them. If the job has already been terminated then the message will be ignored. Control is asynchronous. Rather than trying to set up, e.g., job.population() which returns the current population from a simulation, instead set up job.get_population() which sends a control message to retrieve the population and set up an on_population() method which is called when the population is received on the job message stream. |
Wait for the job to complete. This is used in scripts to impose a synchronous interface to the fitting service. |
| Home | Trees | Indices | Help |
|
|---|
| Generated by Epydoc 3.0.1 on Mon Mar 16 15:03:43 2009 | http://epydoc.sourceforge.net |