[kovidgoyal]

There are various things that are on my TODO list for the CS:

1) The content server can run in two contexts, embedded in the GUI and as a standalone process. When it is embedded in the GUI, you have to setup some mechanism for updating the GUI when the CS make changes. In particular for your question, for a jobs manager this means that it will have to integrate with the GUI job manager when running in the GUI. When running as a standalone process, you need to setup some form of inter-process locking to prevent the GUI from accessing the same library at the same time.

2) The CS needs to be rewritten to use a modern Ajax framework, separating the data from the markup/styling completely, making it easy to theme the server.

3) The CS needs to be refactored to use the new database backend

4) An in browser ebook viewer needs to be added to the CS.

5) Authentication and session management needs to be added along with some kind of system for per user restrictions on viewable libraries/subsets of libraries. We will likely have to move off HTTP digest based auth since the incompetents at google seem to be unable to implement support for it in Android. This means some kind of http form based auth, which is tricky since we cant use ssl in an application server.

6) The content server needs to get support for viewing multiple libraries, this is particularly tricky when running in the GUI and with multiple user sessions. This may actually prove too hard/resource intensive to do at all.

I will start work on 2 and 3 sometime in the relatively near future. It will most likely entail a complete re-write of the server. My plan is to do 2, 3 and 4 and then move on to adding write capabilities to the server. So I would suggest waiting until I am done with 2 and 3 before proceeding, or you will most likely have to redo a lot of work.

Note that adding write support to the current CS is a bad idea since the db backend is not thread safe, which means you will get data corruption/loss when running embedded in the GUI.