Let's please try to avoid stop energy in this thread. <a href="http://www.userland.com/whatIsStopEnergy" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">http://www.userland.com/whatIsStopEnergy</a>
<br><br>On demand sounds great in theory, but let's think about it for a second:
<br>How do you start on-demand a web app? (HTTPD daemon)<br>How do you play the next track when the current track finishes playing? (Kagu daemon, or FastCGI Kagu daemon + HTTPD daemon)<br><br>Kagu
is used very similar to a daemon. It runs as long as you're playing
music. And if that's all you use an n800 for then it's always running.
It might even be in the background if you're taking notes or browsing
the web. The difference is that it has a GUI right now. I'd like to
make that portion optional to save some memory/CPU when you aren't
using it. I'd also like to make startup time faster, and I'd like to
make a web frontend for it.
<br><br>No, I don't mean an always on daemon. I mean an on-demand
daemon. A background process that runs when you need it and doesn't
when you don't.<br><br><br><div><span class="gmail_quote">On 11/26/07, <b class="gmail_sendername">Igor Stoppa</b> <<a href="mailto:igor.stoppa@nokia.com">igor.stoppa@nokia.com</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Hi,<br>On Mon, 2007-11-26 at 13:11 -0500, ext Jesse Guardiani wrote:<br><br>[snip]<br><br>> This would mean that the Kagu backend process would be a daemon (aka a<br>> service, depending on your education environment).
<br><br>If possible, please no, not another daemon. We are already plagued by a<br>large number of (mostly unnecessary!) daemons (i don't remember on top<br>of my head how many exactly, but it's a 2 digits figure) that have
<br>trickled over the years in the standard stack.<br><br>The metacrawler is a good example of why you don't want to write a<br>daemon.<br><br>To write a daemon is to ask for trouble since your sw will use memory,<br>
cpu time and power all the time. Also bugs will be more critical.<br><br>What's wrong with something that runs on-demand?<br><br>Unless you rely on having dbus to start and stop the service ... that<br>would probably be ok.
<br><br><br>--<br>Cheers, Igor<br><br>Igor Stoppa <<a href="mailto:igor.stoppa@nokia.com">igor.stoppa@nokia.com</a>><br>(Nokia Multimedia - CP - OSSO / Helsinki, Finland)<br></blockquote></div><br><br clear="all"><br>
-- <br>Jesse Guardiani<br>Software Developer / Sys Admin<br><a href="mailto:jesse@guardiani.us">jesse@guardiani.us</a>