Special routing strategy for tasks

Brought to you by: danieledipompeo, g_serazzi

#44 Special routing strategy for tasks

Milestone: simulator

Status: wont-fix

Owner: nobody

Labels: Application Improvement (12)

Priority: 5

Updated: 2016-07-30

Created: 2007-07-16

Creator: Bertoli Marco

Private: No

Tasks which are generated from a fork should have a special routing strategy that will discriminate between them and the 'full' jobs.

Discussion

Giuliano Casale - 2016-07-30

status: open --> wont-fix
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
- Anonymous
  
  Add attachments
  Cancel
  You seem to have CSS turned off. Please don't fill out this field.
  
  You seem to have CSS turned off. Please don't fill out this field.

Giuliano Casale - 2016-07-30

This seems ambiguous. Say there are two classes, jobs of class r will be always transformed in tasks and jobs of class s!=r that are not. It is sufficient to specify class-specific routing to address the requirement. I believe it is not possible to have jobs of a given class r that are sometimes forked and sometimes not.

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
- Anonymous
  
  Add attachments
  Cancel
  You seem to have CSS turned off. Please don't fill out this field.
  
  You seem to have CSS turned off. Please don't fill out this field.

Anonymous