F2F Meeting 2011-10-18

• Location: Padova

Participants

• Martin Skou Andersen
• Marco Cecchi
• Alvise Dorigo
• Björn Hagemeier
• others

Common API

The following decisions have been taken during the meeting:

• Need to look at the details now
• Target languages will be Java and C++
  • Python binding will be done using SWIG (responsible Martin)
  • Martin (Arc) and Alvise (CREAM) will share developments
  • Martin and Björn (UNICORE) will define the API in terms of method signatures, which will be aligned as much as possible among Java and C++
• Essentially, the client classes will contain of one client class per service as defined in the EMI ES spec, thus
  • CreateActivity
  • ActivityInfo
  • ActivityManagement
  • ResourceInfo
  • Delegation
• Framework to be used
  • UNICORE is decided, will use their ordinary wsrflite, based on XFire
  • Arc and CREAM will both use libarcclient
  • Martin will help Alvise in starting to use libarcclient

Open issues

• A proposal for package names exists
  • emi-es-client-java
  • emi-es-client-cpp
  • emi-es-client-python
• Needs to be decided, but not difficult nor technically important

Tasks

• Martin, Björn: Define high-level API
• Martin: Packaging of libarc* for better dependency management
• Alvise: low-level stuff (?? don't remember why I wrote this down)

-- BjoernHagemeier - 27-Oct-2011