Typica 1.5 has just been released.

This version brings a lot of new stuff like:

• EC2 enhancements: support for EU and regions,
• SDB enhancements: support for SQL like grammar (select, etc.),
• Bug fixes…
• … and of course the FPS API we’ve been working on.

As Amazon announced plenty of FPS Quick Starts, you now don’t have any excuse for not using the FPS API when developing in Java.

The support for the Amazon FPS API in Typica has been updated in Subversion a few days ago. The support for this API should be available anytime soon within the next release of Typica.

As the FPS API is quite rich and offer lots of different use, feedback is critical in order to test and qualify properly the added support.

We’ve just published a few minutes ago a tutorial explaining how to use Amazon FPS from the excellent Typica library.

Let us know if we should keep working on it and enrich it.

We hope this will help a bit the FPS community.

The slides of the BoF on Elastic Grid and EC2 are finally available!

Thanks for all of you who could come. We had some interesting discussions and feedback after the talk.
This is the first time I had a chance to go to JavaZone and I must say it’s been quite interesting. A few friends and I had the opportunity to discuss with Tom J. Bang who gave us the opportunity to taste local stuff.

I also had the opportunity to discuss with a lot of people there: my friends from our local user group (Guillaume Laforge, Julien Viet, Alexis Moussine-Pouchkine, Jerome Lacoste) but also Scott Davis and Eitan Suez. (Sorry for all the other ones I forgot to cite.)

For those of you who could not make it for our BoF session, the organizers of the JavaZone event will provide a video. I’ll update the blog when the video is available.

I have added a lot of code into the SVN repository in order to provide some experimental support for Amazon FPS.

The current version (revision 186) supports most of the operations you need when you manipulate:

• single use tokens,
• recurring tokens,
• post paid tokens,
• edit tokens.

Basically the current API allow you to generate URL for the CBUI  pipelines, extract information from the request when FPS returns to your site and all the account related APIs, like Account Activity and such.

This code is still in experimental status and I’d like to gather some initial feedback.

What’s left to be done is (ETA: end of the month):

• multi use tokens support,
• prepaid tokens support,
• IPN support.