On Mar 1, 2:19 am, MarkSwanson <mark.swanson...@gmail.com> wrote: > For an example outside of JSON: recently Compojure changed how it > works so the HTTP request properties are all converted to keywords by > default. I can see the appeal, but now anyone using Compojure has the > increased incidental complexity of possible keyword violations. > Imagine if you were integrating with PayPal or some system that had > HTTP parameters with characters that were not allowed by the Clojure > spec. I really don't want to worry about such things when creating > software with Clojure.
Huh? Compojure has pretty much always used keywords in parameter maps. It's certainly not a recent change. For libraries like c.c.json, I agree with you and Stuart, in that the keys should be strings. In fact, I recently argued in the ring-clojure group that the Ring parameter middleware should also use strings, for pretty much the same reasons you have done. Compojure is a slightly different case, because it's a high-level framework, rather than a low-level library. There's a trade-off between convenience and access to low level details. Still; in Compojure 0.4.0 there will be the option of dropping back down to Ring for more direct access to the parameter map if one wishes. - James -- You received this message because you are subscribed to the Google Groups "Clojure" group. To post to this group, send email to clojure@googlegroups.com Note that posts from new members are moderated - please be patient with your first post. To unsubscribe from this group, send email to clojure+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/clojure?hl=en
