-
-
Notifications
You must be signed in to change notification settings - Fork 0
Open
Description
Hi, just checking to be sure I understand correctly from the example given.
- NewJobTracker registers a Worker and it's information, to manage it's own Queue
- A Worker has a pointer to JobTracker, a "job"? and a given Context
What I'm trying to figure out is, what "job" is supposed to be.
As far as I can tell, from how it's used in goop and the filerecurse example, is that it's a "unique" name for the job?
But does it have to be unique? What is it actually used for / what happens when it collides?
I see it being used to spawn a new job using a RecurseWorker inside RecurseWorker, when it encounters a new dir, or in goop each git hash is given it's own job. I'm trying to understand why, and if I can just set it to some static thing and forget about it.
Metadata
Metadata
Assignees
Labels
No labels