SANJEEV BA wrote: > How do we distinguish between the two in IoTivity ? CoAP has inherited this ambiguity from HTTP, which also has no way to distinguish the narrower POST-as-create from the wider catch-all POST-as-an-unspecified-action.
In the HTTP world, we tend to distinguish collection resources from member resources. A collection provides access to a set of links for its members, so updates can be performed directly to the members if needed. This frees POST for a collection to always be the create operation. A POST to a member updates that member. (Note that a member can in turn be another collection, constraining that update to a create, but providing the embedded links again for other updates.) Gr??e, Carsten
