Opened on 06/30/2015 at 01:12:52 PM
Closed on 08/07/2015 at 07:07:42 AM
#2739 closed defect (invalid)
[Send notifications to a subset of the user base] Test notification handler with caching enabled
Reported by: | Ross | Assignee: | |
---|---|---|---|
Priority: | P3 | Milestone: | |
Module: | Sitescripts | Keywords: | |
Cc: | fhd | Blocked By: | |
Blocking: | #2162 | Platform: | Unknown / Cross platform |
Ready: | no | Confidential: | no |
Tester: | Ross | Verified working: | no |
Review URL(s): |
Attachments (0)
Change History (3)
comment:1 Changed on 06/30/2015 at 01:14:00 PM by Ross
- Summary changed from [Send notifications to a subset of the user base] Test with handler with caching enabled to [Send notifications to a subset of the user base] Test notification handler with caching enabled
comment:2 Changed on 06/30/2015 at 01:14:51 PM by Ross
- Ready unset
comment:3 Changed on 08/07/2015 at 07:07:42 AM by fhd
- Resolution set to invalid
- Status changed from new to closed
To answer your question: We're caching requests with the same lastVersion request value for one minute.
However, closing this issue. It's more of a task issue (which we don't have currently, we typically use other systems for that), something we should test. Not exactly a proven defect (yet :D).
Note: See
TracTickets for help on using
tickets.
@fhd How exactly should caching work here?