Open jobol opened 9 years ago
We have --direct in the client, which serves that purpose. For me it would contradict the purpose of providing an API and daemon separation if we enable direct usage through the public API.
Maybe you could elaborate on an instance where the daemon would not be running, but API access (over buxtonctl --direct) would be required?
@ikeydoherty that is how we intend to proceed: if the API doesn't access the server, buxtonctl will be called. That's twisted and unreadable but it will work in our case. However an other idea is to always call buxtonctl.
The --direct option of buxtonctl enforces buxtonctl to use the direct access. That is not something that is predictable and it should be avoided. The opposite option --server is far more useful
When the server is not running, the library libbuxton has no fallback mode to directly access databases. This could be sometime useful.