Issue #30: Split odcs into separate parts - odcs

odcs

#30 Split odcs into separate parts

Closed 6 years ago Opened 6 years ago by cqi.

As we discussed in IRC, it would be great to split odcs to separate parts in order to reuse part of the code and delivery conveniently. The idea is odcs will have three parts,

client, the client API used by any other application to interact with ODCS server.
odcs, the ODCS server.
common, the shared library used by both client and server.

cqi commented 6 years ago

While trying to make subpackage odcs-client, I found odcs/__init__.py is not usable as it contains lots of code that is not relative. This issue should be helpful.

jkaluza commented 6 years ago

Done already.

Metadata Update from @jkaluza:
- Issue status updated to: Closed (was: Open)

6 years ago

Metadata

Assignee

None

Tags

None

Blocking

None

Depending on

None

odcs

Source Code

Documentation

#30 Split odcs into separate parts Closed 6 years ago Opened 6 years ago by cqi.

Metadata

#30 Split odcs into separate parts

Closed 6 years ago Opened 6 years ago by cqi.