bfc9bf80d9
The compositor is moving into a dedicated helper process. That requires a process to launch, channels for Browser and WebContent to talk to it over, and client proxies on each side. Land all of that as an inert scaffold first, gated behind --enable-compositor-process, so the default rendering path is unchanged and later commits can fill in the protocol, the service-side state, and the runtime switch against a stable target.
29 lines
698 B
C++
29 lines
698 B
C++
/*
|
|
* Copyright (c) 2026, the Ladybird developers.
|
|
*
|
|
* SPDX-License-Identifier: BSD-2-Clause
|
|
*/
|
|
|
|
#pragma once
|
|
|
|
#include <Compositor/CompositorWebContentClientEndpoint.h>
|
|
#include <Compositor/CompositorWebContentServerEndpoint.h>
|
|
#include <LibIPC/ConnectionToServer.h>
|
|
|
|
namespace WebContent {
|
|
|
|
class CompositorConnection final
|
|
: public IPC::ConnectionToServer<CompositorWebContentClientEndpoint, CompositorWebContentServerEndpoint>
|
|
, public CompositorWebContentClientEndpoint {
|
|
C_OBJECT_ABSTRACT(CompositorConnection)
|
|
|
|
public:
|
|
explicit CompositorConnection(NonnullOwnPtr<IPC::Transport>);
|
|
|
|
private:
|
|
virtual void die() override;
|
|
|
|
virtual void did_connect() override;
|
|
};
|
|
|
|
}
|