On 6 January 2011 10:43, Markus Korn <thek...@gmx.de> wrote:
> After re-reading this bugreport, the discussion it includes and the merge 
> proposal, I'm still not confident that the API which is proposed here is good 
> enough. This is why I started working on a blacklist API spec.
> It is still work in progress, and I'm not sure if this points in the right 
> direction (comments are welcome) but I at least have a good feeling.
> current version is here: http://paste.ubuntu.com/551001/

I think there is some good stuff in there Markus, however I'm not
entirely sold on the regex idea for lookups. I'd rather that we just
support the same globbing semantics as we do for event templates; ie
prefix-! for negation and postfix-* for truncation. I guess * will be
the most common case. Not allowing general regexes also motivates app
authors to choose more compatible blacklist ids. Ie, we'll be unlikely
to see:


but we encourage something like:


You received this bug notification because you are a member of Zeitgeist
Framework Team, which is subscribed to Zeitgeist Framework.

  Blacklist API sucks

Status in NULL Project:
Status in Unity Files Place:
Status in Zeitgeist Framework:
  In Progress

Bug description:
  Guys, GetBlacklist and SetBlacklist (without any signals) for an 
asynchrounous-by-nature API? Come on!

How about changing it to Get, Add, Remove and a changed signal? That way it'd 
be actually usable...

Mailing list: https://launchpad.net/~zeitgeist
Post to     : zeitgeist@lists.launchpad.net
Unsubscribe : https://launchpad.net/~zeitgeist
More help   : https://help.launchpad.net/ListHelp

Reply via email to