-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 09/14/2010 04:15 PM, Eric Junkermann wrote: > Push notification is something of a myth. There has to be something there > waiting to be pushed. It could be waiting on an event rather than polling, > but then there has to be an event co-ordinator... >
Well, sure. What I'm saying is that said coordinator could then be written as an external program outside of Fossil that, say, uses inotify to check for the presence of a file touched by a post-update hook, then polls the database for changes. If that's not the best solution, then understand that it's what I came up with after 10 seconds of thought. :) I'm not saying that Fossil should be such an event coordinator, just that it would be nice if it could provide some means of notifying such a thing that a change was made. Seems like the exact antithesis of bloat to me, and whatever bloat exists would be written in either site-specific daemons, or some separately-distributed third party utility. Anyhow, it doesn't seem likely that such a thing will be implemented, but regardless of that, I wanted to ensure that folks were clear on what exactly I hoped for. I don't want Fossil to send email notifications or to do anything more than what it already does, and to provide some means of delegating to other parties that doesn't necessarily involve rapid polling of RSS. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkyP57UACgkQIaMjFWMehWIxVwCfanhCg9e71dSgbW8kq5zo0nff 0qEAoIDtXXJEFwM67KPQOQX9sV5ALFYe =wS57 -----END PGP SIGNATURE----- _______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
