I second that.

Basically the batch process communicates its progress via a local log file which the web interface via a simple cgi script reads and then formats the progress. I can also imagine killing the batch job via another cgi script. And spawning a batch job as well, after ticking some boxes on the web interface regarding options/preferences. The web interface can keep track of multiple batch jobs running, via their pid.

The system could equally support 1 user running a single job on their private computer or several users who each logs in and checks their own batch jobs even remotely. Can also send email on certain events.