What are the common ways for deletion local/client objects using REST API?
===

Is there common design pattern for dispatching deleted objects to the requestor (client of the API)?

Challenges we are having:

 1. When object is deleted on the API completely, client will not know
    that object is gone and will keep it locally (as API only shows objects changed after the certain date) 
 2. If we enable object's property to show that is deleted (ex. "deleted = TRUE") then
    eventually number of objects in the API grows and slows down the transfer rate.

Another option we looking into is to have separate Endpoints on the API to show list of deleted objects only (is this the pattern that anyone uses?).
