Tomboy dataprovider should register itself with DataSourceRegistry before pushing events

Bug #691840 reported by Manish Sinha (मनीष सिन्हा) on 2010-12-18
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Zeitgeist Data-Sources
Manish Sinha (मनीष सिन्हा)

Bug Description

As of now tomboy dataprovider simply pushes events. it should register with DataSourceRegistry so that datahub can be sure if at all it is duplicating events. As of now there is no problem, but as per Zeitgeist API best practices, a DP should register itself

Related branches

Talked with ~seiflotfy and confirmed that it is good to have

Changed in zeitgeist-dataproviders:
assignee: nobody → Manish Sinha (manishsinha)
importance: Undecided → Low
milestone: none → 0.2.0
status: New → Confirmed
Changed in zeitgeist-dataproviders:
status: Confirmed → In Progress
Changed in zeitgeist-dataproviders:
status: In Progress → Fix Committed
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers