On Mon, Mar 5, 2012 at 8:49 AM, <org.fossil-scm.fossil-us...@io7m.com>wrote:
> On Mon, 5 Mar 2012 09:23:47 -0500 > Richard Hipp <d...@sqlite.org> wrote: > > On Mon, Mar 5, 2012 at 8:07 AM, > > <org.fossil-scm.fossil-us...@io7m.com>wrote: > > > Ah, yeah, should have explained that. It's essentially just for a > > > notification service similar to that offered by CIA.vc. > > > > I'm not familiar with CIA.vc. But if you just want notifications of > > changes, did you know that Fossil servers have an RSS feed for this? > > Example: > > > > http://www.fossil-scm.org/fossil/timeline.rss > > That's not too bad, but it lacks some metadata we'd like. It also > seems to lump all events (check-ins, tickets, etc) into one stream, > so we'd have to somehow parse it and strip out anything that doesn't > look like a check-in. A query parameter can fix this: http://www.fossil-scm.org/fossil/timeline.rss?y=ci > It's also rather "heavy" in that if, for example, > we're running a server that posts notification messages to an XMPP or > IRC channel, that server has to monitor a potentially large number of > feeds as opposed to (almost blindly) accepting notification > messages from the network. > > I'm not really sure what the most pleasant way to achieve the desired > effect is, but having fossil send a small request to an external server > seemed the easiest to manage in a platform-independent manner (git > commit hooks become pretty unpleasant if developers are working across > different platforms and have to replicate their scripts across all of > their machines). > > -- D. Richard Hipp d...@sqlite.org
_______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
