All, I cut a 1.4 release of Athena tonight. https://github.com/fracturedatlas/ATHENA/downloads In

Hi Gary, I still get 404s with these URLs. Is that expected out of the box until the db is customized

This is semi-off-topic, but Fractured Atlas is also working on a hosted version of ATHENA called

Looks good! One question: is the "sharedWith" property specifically limited to an array of

On Mon, May 9, 2011 at 6:21 PM, Gary Moore <gary....@fracturedatlas.org> wrote: - The patch

We'll ship with it mated to tix, but the code itself is type agnostic and can be used for all

Because of a Jersey update, we can have codes listen at /tix/codes instead of /tix/meta/codes. I

All, This week we found two minor bugs in the Payments component so we shoved the fixes in and cut a

Hey guys, After feedback from Adam and Micah, I renamed "eligibleUsers" to "

All, Starting work on discount codes, one of the flagship features going into 1.1. The README is up

All, I've cut and uploaded the First Release Candidate for Athena. You can download it here:

All, We've spent some time packaging Athena such that you don't need to download a bunch of

Athena code is in beta, and one of our goals in the beta testing period was to put together an easy

Acting on some feedback from Justin Beck as he tried to build ATHENA for the first time, I re-org

I added flags to deploy.rb so you can deploy just one application instead of all of them. Saves time

All, Thanks much for the comments. I propose to use Digest Auth for Authing Client Applications in

I personally like to contain everything to do with a product in one directory tree so that a full

I just pushed out a big change to our github repository. All ATHENA code is now under the ATHENA

Changed the ATHENA-Tix endpoints to: tickets: http://localhost/tix/tickets fields: http://localhost/

GET /payments/transactions/{id} Get details about a payment POST /payments/transactions/authorize

I would vote camelCase over ALL_CAPS. I've done some aliasing on the client side to match

"Token" is a pretty generic term in CS, so there's some inevitable ambiguity. Not sure

Obviously we need to do what we need to do for PCI compliance and we'll leave it to Gary and team

One good option is yamlbeans: http://code.google.com/p/yamlbeans/ Another is to just read a file with

So to summarize querys 1 to 4 are valid and would find Tom, Dick and Harry Query 5 would do a valid

Here at ATHENA Global HQ we're going through what a Payments service would look like. Here are

All, We have released 0.3 and tagged the code in github. We're about to embark on a few big

The transaction flow described below is pretty much set. Micah did point out that our endpoints

Justin, On the POST vs PUT front: the power of a RESTful interface is derived from the uniform

Ryan, Good point about the trust portion of Payments and it leads to how we're handling Client