No websocket equivalent of PUT /things/<thing>/actions/<action>/<id> #85

Activity

1. benfrancis commented on Apr 3, 2018

   

   benfrancis

   on Apr 3, 2018

   Member

   More actions

   I'm not 100% sure this and #84 are actually needed.

   I know the specification says that an action request can be updated with a PUT, but have you come across use cases for this yet? I'm wondering whether action requests should be immutable (by the client) and you should instead send a follow-up action request with the new data?

   This also raises some questions about concurrency and about how to create eventual consistency between the server and all clients.
2. mrstegeman commented on Apr 3, 2018

   

   mrstegeman

   on Apr 3, 2018

   ContributorAuthor

   More actions

   No, I've not yet come across a use case for the PUT. I'd rather just have that removed from the spec, at least for the time being.