An architectural decision to be made, do we want to actually index the data off of every webservice, or just offer 'transparent' backends to query the existing query API's for each service. I'm more for a local copy (makes it fast, and solid even when disconnected, but just my $0.02) I love writing/overhauling new backends, so I might stab at some of these (im actually thinking of maybe an out-of-process script that does its Beagle interaction like the Mozilla extensions ect, so we aren't responsible for its scheduling.)
Anyways, just a little brain-poo. if there's a consensus on design this is a great way to kill time in class ;). On Feb 13, 2008 11:40 AM, Joe Shaw <[EMAIL PROTECTED]> wrote: > Hi, > > On Feb 13, 2008 1:07 PM, D Bera <[EMAIL PROTECTED]> wrote: > > > On Feb 13, 2008 11:43 AM, Dirk Uys <[EMAIL PROTECTED]> wrote: > > > > Other that the TODO list, is there any filters/backends in need of > > > > attension? > > > > I have a fancy one :-) > > Use one of the many C# POP/IMAP libraries to build a gmail backend. > > Conceptually simple, just fetch a bunch of emails (10/15/something > > low) at a time and feed them to beagle. Checkout the other backends on > > how to hook into the scheduler so that the gmail backend is not > > continuously fetching and indexing emails. > > Ah, yes! I knew there was something I was forgetting. > > Integration into wider web services would be nice. As a relatively > recent Gmail user myself, I would be personally grateful for such a > backend. ;) Google Docs, Facebook, Remember the Milk, etc. > > Joe > > _______________________________________________ > Dashboard-hackers mailing list > Dashboard-hackers@gnome.org > http://mail.gnome.org/mailman/listinfo/dashboard-hackers > -- Kevin Kubasik http://kubasik.net/blog _______________________________________________ Dashboard-hackers mailing list Dashboard-hackers@gnome.org http://mail.gnome.org/mailman/listinfo/dashboard-hackers
