Closed Bug 1298971 Opened 10 years ago Closed 10 years ago

notify: api requests to send notifications should be hashed and deduplicated server-side

Categories

(Taskcluster :: Services, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: jonasfj, Assigned: bstack)

Details

tc-client will automatically retry requests that fails.. To mitigate this the server-side should compute hash of address/subject/message or user/channel/message and remember the hash in-memory. If the hash already exists in memory, it should reply 200, but not send the message twice. in-memory dictionary of hashes should be rotated every 1 hour or so. So old entries can be deleted. If we only have one web process this will work fairly well. Presumably we don't need multiple web-processes, if we do need multiple instances, we we have to back this by some cache like redis (which is greate as non-durable cache).
Assignee: nobody → bstack
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
Component: Platform and Services → Services
You need to log in before you can comment on or make changes to this bug.