daemondo defeats purpose of launchd?

I have this problem: the lighttpd web server on my MacBook Pro unexpectedly dies rather frequently (much more frequently than it did on my PowerBook). When this happens, the daemondo process is still there, and I have to use launchctl to unload and then load the lighttpd plist to get the server running again. The point of launchd is that it notices when processes unexpectedly quit, and restarts them automatically so close to no downtime is observed. But launchd is monitoring daemondo, which does not exit, so launchd does not restart anything. And daemondo doesn't seem to have the same process-death-noticing feature so daemondo is not automatically restarting the failed lighttpd. Comments?