Re: [ANN] Amazonica: Clojure client for the entire AWS api

There is already a default release script included with recent versions of Leiningen. To do a release, simply run lein release :major, :minor, or :patch depending on the version bump that you want. -- Daniel > On 23/11/2014, at 1:06 pm, Sam Ritchie wrote: > > If you guys feel strongly, I'm su

Re: [ANN] Amazonica: Clojure client for the entire AWS api

If you guys feel strongly, I'm sure the Amazonica maintainers would love a pull req that adds a small release script that handles this for them. I'm sure it'd get merged, and it'd be a nice, constructive way to move the discussion forward. Gary Verhaegen Nove

Re: [ANN] Amazonica: Clojure client for the entire AWS api

On Thursday, 20 November 2014, Michael Cohen > wrote: > > - There are no releases or tags on github > Again, I didn't really know what I was doing here, and never really > changed the approach. What do people expect, a snapshot release for > current development, and periodic version bumps and relea

Re: [ANN] Amazonica: Clojure client for the entire AWS api

Regarding releases, the lein release function gives you good defaults for releasing Clojure projects, it handles tagging, commit messages, and versioning. https://github.com/technomancy/leiningen/blob/master/doc/DEPLOY.md#releasing-simplified has details. -- Daniel > On 21/11/2014, at 1:08 p

Re: [ANN] Amazonica: Clojure client for the entire AWS api

Hi Greg, I think all of your criticisms are very valid, and I think I've seen most of them voiced by others at various times. I wrote it in about 3 weeks in March of 2013, when I was very new to Clojure, so I'm sure I made lots of mistakes. I was using some Java with AWS and some Clojure, with Jam

Re: [ANN] Amazonica: Clojure client for the entire AWS api

Good discussion, Greg. I'll add my two cents, point by point: > * The documentation is sparse and the code is not self-documenting. I've occasionally had some trouble in this area, but I actually do find that it's not too hard to map from the Java AWS api directly to clojure. For example, this c

Re: [ANN] Amazonica: Clojure client for the entire AWS api

I just wanted to say that while amazonica is also my AWS library of choice, and I'm so glad it exists, and "running code wins", I also run into all the same issues that Greg listed. On Thu, Nov 20, 2014 at 12:32 PM, Greg Mitchell wrote: > Thanks for creating this library, Michael. Your solution

Re: [ANN] Amazonica: Clojure client for the entire AWS api

Thanks for creating this library, Michael. Your solutions for writing the library are creative for sure, and this library has helped with developing with AWS. However, I've been using the amazonica library to communicate with AWS components in an enterprise-scale project for about a year now, a

Re: [ANN] Amazonica: Clojure client for the entire AWS api

probably not. amazonica delegates to the official java sdk. On Tue, Oct 21, 2014 at 4:12 AM, Yehonathan Sharvit wrote: > Do you plan to have a cljs version of America > > It would ne nice if you could support s3 api. > > > On Monday, 25 March 2013 23:51:42 UTC+2, Michael Cohen wrote: >> >> Curio

Re: [ANN] Amazonica: Clojure client for the entire AWS api

Do you plan to have a cljs version of America It would ne nice if you could support s3 api. On Monday, 25 March 2013 23:51:42 UTC+2, Michael Cohen wrote: > > Curious to hear opinions on this: > > https://github.com/mcohen01/amazonica > -- You received this message because you are subscribed t

Re: [ANN] Amazonica: Clojure client for the entire AWS api

I know this is an old thread ... but FWIW I think this is awesome. Great work, Michael! I am going to play around with it. On Thursday, March 28, 2013 10:31:00 PM UTC-7, Michael Cohen wrote: > > I ran a quick and dirty benchmark comparing Amazonica with James' rotary > library, which uses no exp

Re: [ANN] Amazonica: Clojure client for the entire AWS api

I ran a quick and dirty benchmark comparing Amazonica with James' rotary library, which uses no explicit reflection. This was run from an EC2 instance in East, hitting a Dynamo table in the East region. tl;dr Amazonica averaged 9ms for gets, rotary averaged 6ms, both averaged 13ms for puts. Su

Re: [ANN] Amazonica: Clojure client for the entire AWS api

2013/3/26 Hugo Duncan > > Or can the cost be confined to compile time... > That would be nice to have! Generating type-hinted clojure code from the reflection result and emitting that with macros would be an option. I think the dynamic use of reflection would be enough to put me off > using thi

Re: [ANN] Amazonica: Clojure client for the entire AWS api

Michael Cohen writes: > Well, of course everything is handled via reflection, which has a cost. The > question is, can you afford the cost. Or can the cost be confined to compile time... > In general, I think most of the AWS > apis really aren't concerned with performance, e.g. EC2, and you'

Re: [ANN] Amazonica: Clojure client for the entire AWS api

Well, of course everything is handled via reflection, which has a cost. The question is, can you afford the cost. In general, I think most of the AWS apis really aren't concerned with performance, e.g. EC2, and you're not making (many) repeated calls. If you look at something like DynamoDB thou

Re: [ANN] Amazonica: Clojure client for the entire AWS api

I'm a bit concerned about all the reflection going on. Am I correct that the lib does dynamic dispatch at runtime based on both the arity and the number of arguments? The code looks like it would be painfully slow. Perhaps the hit is okay if I only want to make a dozen calls a second or so, but if

Re: [ANN] Amazonica: Clojure client for the entire AWS api

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:

Re: [ANN] Amazonica: Clojure client for the entire AWS api

2013/3/26 James Reeves > 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 ge

Re: [ANN] Amazonica: Clojure client for the entire AWS api

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 :) - James On 25 March 2013 21:51, Michael Cohen wrote: > Curious to hear opinions on this: > > https://github.com/mcohen01/amaz

Re: [ANN] Amazonica: Clojure client for the entire AWS api

Good one! That's just what I wanted to add cloudfront invalidation in my cms. Thanks! I suspect, that some of the reflective support code you implemented there, might be a good fit for the java.data contrib. -- -- You received this message because you are subscribed to the Google Groups "Clojur

[ANN] Amazonica: Clojure client for the entire AWS api

Curious to hear opinions on this: https://github.com/mcohen01/amazonica -- -- 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 pati