Thanks for the comments. I've made the suggested changes such that the AWS functions take an optional first parameter map of credentials. But I'm left wondering if it should not be required, and just do away with the stateful "defcredential" convenience. Thots?
On Monday, March 25, 2013 6:29:49 PM UTC-7, Herwig Hochleitner wrote: > > 2013/3/26 James Reeves <ja...@booleanknot.com <javascript:>> > >> It looks very interesting, but I'm afraid I really don't like >> "defcredential" macro. The Clojure API should really have *less*mutability >> than the Java API, not more :) >> > > Agreed! It would be nicer to pass a context to the api functions. > > The api functions could be generated such to expect an optional first > context argument and otherwise expect a dynamic binding. > IMO it would also be acceptable to unconditionally take a context > argument, because we have doto. > -- -- 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 --- You received this message because you are subscribed to the Google Groups "Clojure" group. To unsubscribe from this group and stop receiving emails from it, send an email to clojure+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
