Skip to content

Design and Scope Constraints

oweidner edited this page Mar 10, 2012 · 1 revision
  • Eventually, Bliss will support async ops
  • Eventually, Bliss may support monitoring
  • Bliss will not support late binding
  • Bliss' API scope / completeness will be dominated by ease of implementation and user demand
  • Bliss will strive to have limited dependencies (only PyPi dependencies are accepted)
  • Replica, Advert and Message API may (or may not) get added as needed
  • Loose binding is preferred for plug-ins (e.g., they should invoke command line tools instead of implementing a protocol)
  • Modulo above constraints, bliss will strive to be faithful to the SAGA API specs.