mirror of
https://github.com/logos-co/logos-cpp-sdk.git
synced 2026-08-31 09:41:06 +00:00
Iuri MatiasandLogos Workspace
4197ee1830
* refactor: abstract connection/transport; and clearly separate qt remote obj and qt local into separate implementations * abstract qt remote registry * add mock implementation; these serves to further test the abstraction but also useful for testing modules later * use LogosObject instead of QObject * abstract provider side * updates to use new api * re-add async api back --------- Co-authored-by: Logos Workspace <logos@workspace.local>
32 lines
1004 B
C++
32 lines
1004 B
C++
#ifndef LOGOS_REGISTRY_H
|
|
#define LOGOS_REGISTRY_H
|
|
|
|
/**
|
|
* @brief Abstract interface for a module registry endpoint.
|
|
*
|
|
* A registry is a well-known rendezvous point that modules advertise
|
|
* themselves on (host/provider side) and that consumers discover them
|
|
* through (client side).
|
|
*
|
|
* The interface is intentionally minimal: lifecycle management
|
|
* (creation / destruction) is handled entirely by the implementation's
|
|
* constructor and destructor. Callers only need to check whether the
|
|
* registry is up and running.
|
|
*
|
|
* Current implementations:
|
|
* - QtRemoteRegistry — backed by QRemoteObjectRegistryHost (Remote mode)
|
|
* - NullRegistry — no-op used in Local (in-process) mode
|
|
*/
|
|
class LogosRegistry {
|
|
public:
|
|
virtual ~LogosRegistry() = default;
|
|
|
|
/**
|
|
* @brief Returns true if the registry endpoint has been successfully
|
|
* created and is ready to accept registrations.
|
|
*/
|
|
virtual bool isInitialized() const = 0;
|
|
};
|
|
|
|
#endif // LOGOS_REGISTRY_H
|