http - REST PUT vs POST with UUID -



http - REST PUT vs POST with UUID -

if using uuid identify entity part of uri of rest endpoint:

/entities/<uuid>/

and uuid generated client when creating new entities, there best practice far using put vs post? in other words uuid generated client opposed server.

if utilize put, expected message payload contain uuid well? in case both message uri identifying entity contain uuid.

for spec, see: rest rfc

since (the client) know uuid, put best practice, , don't need include uuid in payload. admittedly, put vs post controversial , reading , re-reading rfc doesn't totally clear me. think preceding orthodoxy.

see put vs post in rest nice discussion.

rest http post routing put

Comments

Popular posts from this blog

maven fortify plugin : Unable to load build session with ID XXXXX .. See log file for more details -

c# - Primavera WebServices does not return any data -

android - Display emoji panel with genymotion - keyboard/touch input? -