Home/ Questions/Q 288679
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-12T05:50:21+00:00

Scenario Imagine a REST service that returns a list of things (e.g. notifications) Usage

  • 0

Scenario Imagine a REST service that returns a list of things (e.g. notifications)

Usage A client will continually poll the REST service. The REST service retrieves records from the database. If records are available, they are converted into JSON and returned to the client. And at the same time, the retrieved records are purged from the DB.

Problem How do you handle the problem if the REST endpoints encounters a problem writing the results back to the client ? By that time, the records have been deleted.

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    Deleting the records will always be a dangerous proposition. What you could do instead is include a timestamp column on the data. Then have your REST url include a “new since” timestamp. You return all records from that timestamp on.

    If the notifications grow to be too large you can always setup an automated task to purge records more than an hour old – or whatever interval works well for you.

    • 0