more comment work
This commit is contained in:
parent
efc0b2e28e
commit
0ec0ad42bc
1 changed files with 4 additions and 1 deletions
|
@ -10,9 +10,12 @@ Should preferably also be able to tell when a server is just gone and stop bothe
|
||||||
|
|
||||||
|
|
||||||
Implementation idea: New job gets send to queue (via function call). Queue then launches a new goroutine for that job
|
Implementation idea: New job gets send to queue (via function call). Queue then launches a new goroutine for that job
|
||||||
Goroutine then launches multiple new goroutines, one per targeted inbox
|
Goroutine then launches multiple new goroutines, one per targeted inbox, filtered by blocked targets
|
||||||
Each of those will wait for a ticker or a stop signal
|
Each of those will wait for a ticker or a stop signal
|
||||||
On each ticker they'll try to deliver the payload to the target inbox
|
On each ticker they'll try to deliver the payload to the target inbox
|
||||||
If a stop signal comes in, push the payload and goal into the db to pick up again later
|
If a stop signal comes in, push the payload and goal into the db to pick up again later
|
||||||
On stop or sucessful delivery, exit the goroutine
|
On stop or sucessful delivery, exit the goroutine
|
||||||
|
Stop can also be used to suspend outbound traffic to another instance to help reduce the load on them
|
||||||
|
|
||||||
|
TODO: Think of ways to make this more configurable for how data is being sent how fast
|
||||||
*/
|
*/
|
||||||
|
|
Loading…
Reference in a new issue