From f6d85be52830d17dbf6e7b01bf854a49dccbc7f8 Mon Sep 17 00:00:00 2001 From: Andrew Tridgell Date: Sun, 12 Sep 2010 10:02:02 +1000 Subject: s4-messaging: add support for no_reply in irpc messages It can be useful for a irpc message to be one-way, where the client sends a messages and the server does not reply. This will be used for things like a triger message from an auth context to the drepl server to tell it to try a REPL_SECRET on a user in a RODC. Previously we've used raw messaging for messages that have no reply, but that doesn't allow us to use messages described by IDL Pair-Programmed-With: Andrew Bartlett --- source4/lib/messaging/irpc.h | 1 + 1 file changed, 1 insertion(+) (limited to 'source4/lib/messaging/irpc.h') diff --git a/source4/lib/messaging/irpc.h b/source4/lib/messaging/irpc.h index 4b497959ee..2a76461954 100644 --- a/source4/lib/messaging/irpc.h +++ b/source4/lib/messaging/irpc.h @@ -35,6 +35,7 @@ struct irpc_message { struct irpc_header header; struct ndr_pull *ndr; bool defer_reply; + bool no_reply; struct messaging_context *msg_ctx; struct irpc_list *irpc; void *data; -- cgit