Files
logos-protocol/cpp/logos_types.cpp
T
Dario Lipicar 29afbac532 Extract the Logos protocol layer from logos-cpp-sdk (lp_* C ABI + protocol semver) (#2)
* Extract the Logos protocol layer from logos-cpp-sdk

Transports (plain TCP/TLS, qt_local, qt_remote/QRO, mock), token manager,
consumer core (LogosAPIClient/LogosAPIConsumer incl. the capability
auto-requestModule flow), ModuleProxy, the abstract LogosProviderObject
interface, and the canonical QVariant<->JSON conversion — now behind the
language-neutral lp_* C ABI (logos_protocol.h) carrying the protocol
semver (LOGOS_PROTOCOL_VERSION_*, lp_protocol_version()).

Bytes crossing the ABI use the lossless {"_bytes": base64url} tagging
(NUL-safe), matching the plain wire encoding.

Provider lp_* surface is compiled groundwork; serving lands with module
authoring.

* consumer: typed requestModule for the capability flow

Port of logos-cpp-sdk master f5a127dd ('use updated capability module',
cpp-sdk#85, Iuri Matias) — the touched files (logos_api_client.cpp,
logos_api_consumer.{h,cpp}) moved into this repo in the P1 extraction.
The capability auto-requestModule path now calls a typed std::string
helper on the consumer (which acquires the capability object directly)
instead of a stringly invokeRemoteMethod round-trip. 111/111 tests.
2026-06-12 18:59:01 -03:00

16 lines
680 B
C++

#include "logos_types.h"
// All three fields. The `error` field used to be dropped on the wire —
// senders set it, receivers got a default-constructed (null) QVariant —
// so any failed LogosResult looked like a success path with no explanation.
// Daemon and modules always build from the same SDK (they ship together in
// the same process group) so extending the wire format is safe.
QDataStream& operator<<(QDataStream& out, const LogosResult& result) {
out << result.success << result.value << result.error;
return out;
}
QDataStream& operator>>(QDataStream& in, LogosResult& result) {
in >> result.success >> result.value >> result.error;
return in;
}