In article <cakr6gn061vxn2t_uacanka6mydaewujyz6ck3b9rc5hxgvt...@mail.gmail.com> you write: >Bearing in mind that I like being a purist and could understand the >GET/POST thing in terms of architecture, I'm asking myself if it makes >sense to use GET URL semantics which require super-encoding things to >fit into URL norms, or to use POST semantics where the block of data >might be constrained by what we want to say, but the MIME encodings >are there to make it easier to say what it is, and why its encoded >that way.
I went back and looked at the http 1.1 spec, which says that GET is idempotent and intended for reading stuff, PUT is not and intended for writing stuff, and POST may or may not be and does whatever it does. So POST to fetch data feels yucky, but I don't see it as so yucky as to demand that they use GET with the query encoded into the URL path. R's, John _______________________________________________ DNSOP mailing list DNSOP@ietf.org https://www.ietf.org/mailman/listinfo/dnsop
