moved LazyFileAppender to util and made sure it's properly configured by the coaster service
shorter wait on worker shutdown
removed channel configuration; none of the fancy fault tolerant channel stuff was being used
fixed sockets not being closed issue
allow setting ServiceContact-valued objects
no more channel configuration, as I was saying
increase shutdown watchdog delay and allow non-existing CPUs to be removed when shutting down to make it easier to bulk-remove them
fixed some races and make sure to close socket properly; removed shutdown() method (which sent the channel shutdown command to the service) and use the ServiceShutdownCommand instead, which is specific to the coaster service, and does some extra stuff; also, I have no idea how to call shutdown(sockFD) if the current object has a shutdown() method without inelegantly writing a wrapper function
fixed a segfault, increased select timeout to 1 second, and fixed a locking issue
fixed final flag not being set
added settings needed to use the actual coaster worker stuff
I apologize in advance. * Removed all the fancy channel re-connection and buffering stuff (it was not used by swift), moved the ChannelContext idea into the channels themselves (since the context is not needed outside of a channel), and simplified the ChannelManager implementation. * Added a shared mode for the coaster service, where the configuration is fixed and read from a file, and multiple clients share workers. * Properly implement cleanup and sharing when multiple clients are involved. * Properly handle client disconnects. * Drop the remote job ids as far as the client is concerned (only use them internally). * Allow block provider/jobManager/url to be provided via Settings instead of just some ill-specified portion of the job description.
removed channel configuration, and removed handling of remote job id since notifications are now sent using the local id; the use of separate remote ids caused issues: sometimes notifications about a job could arrive before the service replied to the submit command with a remote id; also fixed some locking issues; added a method to wait for at least one job to complete
removed remote identity from job
send reply to status command before notifying listeners about the job status; it would be hard to guarantee otherwise that the reply makes it back if the client shuts down as a reaction to a job completing
added tool to test submission of multiple jobs with concurrency and stuff
updated...