[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[alto] draft-penno-alto-protocol-03 - Use of POST for queries



Hi folks,

I'm giving a deeper look to the ALTO restful interface proposed in the
draft and I'm wondering about the reason to have POST to handle some
kind of queries.
For example, one form of Reverse (pid) Property Lookup is:

Method: POST
URI Path: '/prop/pid/m'
Body: an XML document containing a list of PIDs

Instead, what about something like:

Method: GET
URI Path: '/prop/pid/m'
URI QS Params:'name=[pidname]' (multiplicity: 1..*)
Body: MUST be empty

It looks more restful: in the end these queries are read operations, and
GET is the appropriate method for reads. Furthermore the parameters
needed by the queries are not complex or structured enough to justify
the need of an XML document to represent them: query parameters may
suffice. It also avoids possible confusion that may arise in using the
same XML structure (the one that will be specified in Appendix B.5) for
both request parameters and response body.
Is there any specific reason to need POST with XML body?

Best Regards,
Antonio Fusco

--
_________________________________________________
Telecom Italia
Antonio Fusco
Control, Service Layer & Applications
Service Layer & Messaging Innovation & Engineering
Via Reiss Romoli, 274 10148 Torino
+39 011 228 5124
+39 3316001359


Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie.

This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks.


Note Well: Messages sent to this mailing list are the opinions of the senders and do not imply endorsement by the IETF.