forked from bitcoin/bitcoin
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Add ipc::Context and ipc::capnp::Context structs
These are currently empty structs but they will be used to pass some function and object pointers from bitcoin application code to IPC hooks that run, for example, when a remote object is created or destroyed, or a new process is created.
- Loading branch information
Showing
7 changed files
with
62 additions
and
2 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,23 @@ | ||
// Copyright (c) 2021 The Bitcoin Core developers | ||
// Distributed under the MIT software license, see the accompanying | ||
// file COPYING or http://www.opensource.org/licenses/mit-license.php. | ||
|
||
#ifndef BITCOIN_IPC_CAPNP_CONTEXT_H | ||
#define BITCOIN_IPC_CAPNP_CONTEXT_H | ||
|
||
#include <ipc/context.h> | ||
|
||
namespace ipc { | ||
namespace capnp { | ||
//! Cap'n Proto context struct. Generally the parent ipc::Context struct should | ||
//! be used instead of this struct to give all IPC protocols access to | ||
//! application state, so there aren't unnecessary differences between IPC | ||
//! protocols. But this specialized struct can be used to pass capnp-specific | ||
//! function and object types to capnp hooks. | ||
struct Context : ipc::Context | ||
{ | ||
}; | ||
} // namespace capnp | ||
} // namespace ipc | ||
|
||
#endif // BITCOIN_IPC_CAPNP_CONTEXT_H |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,19 @@ | ||
// Copyright (c) 2021 The Bitcoin Core developers | ||
// Distributed under the MIT software license, see the accompanying | ||
// file COPYING or http://www.opensource.org/licenses/mit-license.php. | ||
|
||
#ifndef BITCOIN_IPC_CONTEXT_H | ||
#define BITCOIN_IPC_CONTEXT_H | ||
|
||
namespace ipc { | ||
//! Context struct used to give IPC protocol implementations or implementation | ||
//! hooks access to application state, in case they need to run extra code that | ||
//! isn't needed within a single process, like code copying global state from an | ||
//! existing process to a new process when it's initialized, or code dealing | ||
//! with shared objects that are created or destroyed remotely. | ||
struct Context | ||
{ | ||
}; | ||
} // namespace ipc | ||
|
||
#endif // BITCOIN_IPC_CONTEXT_H |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters