=-runtime support: should we eventually just go with APR, glib, maybe something from suckless people? Is libdaemon (or whatever's out there) useful?
=-XML (XML-RPC): useful as a communication protocol? as RPC protocol? see atheme; useful as job description format possibly.
B-remoteio: figure out how to handle communications; async + callbacks seems the best method to me atm
Master
?*-update frame assigner to distribute some frames for lower-priority jobs when there's a higher priority job (Ask LordOfWar if this is implemented in sprocs already)
B/E/?-Add calls to remotio -> make API for sending messages ~= a function for every type of message defined in protocol.h (are SendSignal() and SendExtSignal() good enough?)
a-XML-RPC interface for obtaining info
=-charsets: the program should operate in UTF-8. This is partially required by libxml2's (and XML's) usage of UTF-8. We want the program's internal charset to be UTF-8 and figure out if we need w_char/whatever to fulfill UTF-8. I don't believe we do... mabye we just need a declaration that al data stored must be in UTF-8 format. -> we need to consider how charsets work when and if issues come up
*-figure out delete-during-traversal with liblist
*-after job is complete and verified by the user, tar frames for easy download
x-Complete testing with interactive test mode
x-Complete DB testing with php server workaround
x-resolve conflict between liblist and libmysqlclient
x-update frame assigner to distribute some frames for lower-priority jobs when there's a higher priority job (Ask LordOfWar if this is implemented in sprocs already(it is))
Slave
E-Backport SimpleSlave functionality to slave code
B-UnpackJob() and supporting functions need to work
E-Restore tar functionality after unpackJob() is functional
E-Add calls to remoteio, once it works or even before it works -> write message API functions and API