IntenseWebs/gitea
3
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Document the queue item's marshaling behavior (#27271)

Browse Source 
Close #26843
This commit is contained in:
wxiaoguang 2023-09-26 13:58:57 +08:00 committed by GitHub
parent 3f82ca38af
commit d0012c8806
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 2 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
modules/queue/queue.go
View File

@ -9,6 +9,8 @@
// - An item can be a simple value, such as an integer, or a more complex structure that has multiple fields. // - An item can be a simple value, such as an integer, or a more complex structure that has multiple fields.
// Usually a item serves as a task or a message. Sets of items will be sent to a queue handler to be processed. // Usually a item serves as a task or a message. Sets of items will be sent to a queue handler to be processed.
// - It's represented as a JSON-marshaled binary slice in the queue // - It's represented as a JSON-marshaled binary slice in the queue
// - Since the item is marshaled by JSON, and JSON doesn't have stable key-order/type support,
// so the decoded handler item may not be the same as the original "pushed" one if you use map/any types,
// //
// 2. Batch: // 2. Batch:
// - A collection of items that are grouped together for processing. Each worker receives a batch of items. // - A collection of items that are grouped together for processing. Each worker receives a batch of items.