Contents

[o] scheduled jobs : do not use delayed jobs
[x] put_back in the operate loop ?
[x] test with beanstalk -b ruote_work/beanstalk/ or something
    no need for beanstalk binlog
[o] drop the msgs idiosyncrasies ?
    at first try to go all the way with msgs vs commands
    |
    one of the disadvantages of msgs + commands is that
    schedules are not stored at the same place as the exps/workitems/...
[o] fork beanstalk S(d, 'iface:port', :fork => true)
[o] operate : sign messages (tube AND timestamp)
[o] security issue in #serve (send)
[o] receiver : launchitem ?
[o] 'commands' channel : better name ?
[o] rw : document participant / receiver (use bs as an example)
[o] storage.close
[o] ParticipantProxy ?
[x] operate : better name ?
[x] what about receiver connections that timed out ? Is it possible ?

[x] base64 encode/decode to allow for non-ascii values
    => add some 漢字 test to ruote/test/unit/storage.rb
    This is a beanstalk-client vs ruby 1.9.x problem

[ ] follow example of latest ruote-amqp (for what ?)

Version data entries

2 entries across 2 versions & 1 rubygems

Version	Path
ruote-beanstalk-2.2.0	TODO.txt
ruote-beanstalk-2.1.11	TODO.txt