summaryrefslogtreecommitdiff
path: root/doc/todo/wishlist:___39__get__39___queue_and_schedule.
diff options
context:
space:
mode:
authorGravatar anarcat <anarcat@web>2015-04-28 21:32:36 +0000
committerGravatar admin <admin@branchable.com>2015-04-28 21:32:36 +0000
commit83e43bbde27150effce78855c77cfc0a04cd34ed (patch)
tree00465c7ae34aea807057d822b49207d6f045ca1d /doc/todo/wishlist:___39__get__39___queue_and_schedule.
parent54123fa73fd8979d80c671ce464b7a157601db56 (diff)
Added a comment: how does the queue get built now?
Diffstat (limited to 'doc/todo/wishlist:___39__get__39___queue_and_schedule.')
-rw-r--r--doc/todo/wishlist:___39__get__39___queue_and_schedule./comment_1_d6ab311beee2ce5f73ae325a4ae463d4._comment11
1 files changed, 11 insertions, 0 deletions
diff --git a/doc/todo/wishlist:___39__get__39___queue_and_schedule./comment_1_d6ab311beee2ce5f73ae325a4ae463d4._comment b/doc/todo/wishlist:___39__get__39___queue_and_schedule./comment_1_d6ab311beee2ce5f73ae325a4ae463d4._comment
new file mode 100644
index 000000000..df273afb2
--- /dev/null
+++ b/doc/todo/wishlist:___39__get__39___queue_and_schedule./comment_1_d6ab311beee2ce5f73ae325a4ae463d4._comment
@@ -0,0 +1,11 @@
+[[!comment format=mdwn
+ username="anarcat"
+ subject="how does the queue get built now?"
+ date="2015-04-28T21:32:36Z"
+ content="""
+how does the queue get created now? is it random or is there some deterministic thing that could be abuse to prioritise some content already (say alphabetical order or some similar hack)?
+
+the scheduling I think i can work around with clunky cron jobs to start/stop the assistant, but the queue I feel is a different beast. would you be available for hire to implement this feature in priority?
+
+thanks!
+"""]]