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

[mrstegeman]

No description provided.

[benfrancis]

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.

[mrstegeman]

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.