James M Snell wrote: > > Well, the fact that APP doesn't define a behavior for the POST operation > on member resources gives you a head start on defining this as an > extension. > > A quick and dirty solution would be to augment POST with an Method > header that identifies the actual method the user wishes to perform. > > E.g. for delete, it would be > > POST /member-uri HTTP/1.1 > Host: example.org > Method: DELETE
Use a URL instead of [TEXT]. Slap the HTTP DELETE/PUT URI values in some IANA registry that takes 6 months to process a registration. Job done. That imo, is better than trying to map methods onto magic URIs, or embed verbs in pub:control, which I suspect is what people will try and do before looking to HTTP headers. In the beginning there was the verb. We've been here before. These are worth reading: CarrotVsOrange DifferentlyAbledClients PutDeleteSupport PutDeleteFaq It's interesting that PutDeleteSupport just got an update after 13 months. cheers Bill
