On Thu, Jan 10, 2013 at 5:18 AM, Jörn Kottmann <[email protected]> wrote:
> Well, you can easily support both use cases by defining a Java API and on > top of that you define a rest API. > Depending on your need you now choose which parts you want to use. If you > want to embed it you just take > the Cas store Java API plus an implementation of (e.g. in your case based > on Lucene and HSQLDB). > At the OAQA project we follow that approach, we use a provider-agnostic Java interface and configurable runtime persistence providers depending on the use case. This allows us to use a SQL database for large scale experiments, or an embedded database that developers can instantiate from Eclipse.
