The current aim of the 0.6.0 release is to have a way of storing jobs and their statuses.

Both the scheduler and the storage are now used as traits and not as concrete implementations. The storage data of the jobs are sequenced using Prost! Protobufs. This allows for the bytes of a job to be stored and retrieved from the job store and then sequenced back into concrete jobs. For beta 1, the existing functionality of in-memory storage are implemented accordingly and considered stable. That is - nothing should break if you use this over 0.5. If it breaks, please file a bug report.

For the user facing API, nothing huge has changed. However, I've added JobSchedulerError as my enum of when things go wrong, replacing Box<dyn Error> in most of the places.

For beta 2, I'll be aiming for Nats.io storage, as this is the itch I wanted to scratch with this crate (end game for my use). I do see the current layout of the code like I wanted it to be for me to implement the Nats.io storage, as it follows a sort-of message driven way of creating jobs and notifications.

Comments are welcome! Speaking of comments - there are lots more eprintln! in this crate now. Please comment if you'd rather not have me implement errors using the log crate. This will be done in beta 2 barring any requests not to.