You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There is a mechanism in place to delete old requests, to save disk space and let the application perform better. The deletion of requests is now, however, done after every performed request.
Describe Preferred Solution
It would be better if a the application has a scheduled job that would execute the deletion of old requests. This way, the request execution is not responsible anymore for deleting the old requests. A larger number of requests may still be available in HttPlaceholder that still need to be cleaned, until the scheduled job has been executed. A con for HttPlaceholder instances that are hosted in the cloud and use a serverless database, is that when the scheduled job runs, extra costs might occur. To combat this, the old option of deleting old requests after the execution of a request, should still be possible. This should be configurable by using a configuration option. So the option is either to clean old requests using the scheduled job OR after every executed request.
Describe Alternatives
Related Code
Additional Context
If the feature request is approved, would you be willing to submit a PR?
Yes / No (Help can be provided if you need assistance submitting a PR)
The text was updated successfully, but these errors were encountered:
Feature Request
Describe the Feature Request
There is a mechanism in place to delete old requests, to save disk space and let the application perform better. The deletion of requests is now, however, done after every performed request.
Describe Preferred Solution
It would be better if a the application has a scheduled job that would execute the deletion of old requests. This way, the request execution is not responsible anymore for deleting the old requests. A larger number of requests may still be available in HttPlaceholder that still need to be cleaned, until the scheduled job has been executed. A con for HttPlaceholder instances that are hosted in the cloud and use a serverless database, is that when the scheduled job runs, extra costs might occur. To combat this, the old option of deleting old requests after the execution of a request, should still be possible. This should be configurable by using a configuration option. So the option is either to clean old requests using the scheduled job OR after every executed request.
Describe Alternatives
Related Code
Additional Context
If the feature request is approved, would you be willing to submit a PR?
Yes / No (Help can be provided if you need assistance submitting a PR)
The text was updated successfully, but these errors were encountered: