I would like to better understand the chemistry-api module. It's
probably easiest to describe my current understanding and ask
questions, then you can correct me where applicable.
My understanding...
The intent is to provide:
1) Java API for clients who wish to interact with a CMIS server that's
simple to use and independent of protocol binding.
2) Java SPI for:
a) repository providers who wish to add a CMIS provider facade
to their repository
b) protocol providers who wish to map CMIS client requests to
protocol and map protocol to CMIS provider
3) An API to SPI adaptor (for in-process access to provider, or
protocol access to provider via API)
Questions...
1) chemistry-api seems to consist of both API and SPI which are
dependent on each other. Is that correct? Or is chemistry-api
currently only focused on SPI?
2) What is the relationship between SPI, Repository and Connection?
3) For a CMIS client of chemistry-api what is the typical call
sequence for interacting with a CMIS server? I assume...
a) get Repository (with protocol specific factory)
b) Repository.getConnection() (although Repository also
provides access to types and SPI outside of connection)
c) connection.xxx()
d) connection.close()
4) Is it the plan to allow Credentials to be provided to the API? e.g.
on establishing connection
5) Will RepositoryService eventually be the entry-point for a client?
6) Is it the plan to provide a factory mechanism (like JCR) for
providing the entry-point API interface, bound to a chosen and
configured SPI client protocol implementation?
Sorry, lots of questions. I understand things are moving quickly, Just
getting up to speed.
Regards,
Dave
