I wanted to gather your opinions on an idea we have for the Project Haystack standard regarding the hisWrite endpoint. Many times, we come across instances where smart devices that emit data to our system, which implements the Project Haystack standards, experience clock discrepancies or scaling issues.
We thought it would be great to have an endpoint that allows us to delete data that was previously written using the hisWrite endpoint. What do you all think about this proposal? If you find it appropriate, should we consider implementing the hisDelete endpoint, or would it be more suitable to use the HTTP [DELETE] method with the hisWrite endpoint?
Samuel Toh Mon 15 May 2023
Hi everyone,
I wanted to gather your opinions on an idea we have for the Project Haystack standard regarding the hisWrite endpoint. Many times, we come across instances where smart devices that emit data to our system, which implements the Project Haystack standards, experience clock discrepancies or scaling issues.
We thought it would be great to have an endpoint that allows us to delete data that was previously written using the hisWrite endpoint. What do you all think about this proposal? If you find it appropriate, should we consider implementing the hisDelete endpoint, or would it be more suitable to use the HTTP [DELETE] method with the hisWrite endpoint?
Looking forward to hearing your thoughts!