Answer the question
In order to leave comments, you need to log in
Can ETW implement a client/server architecture with the register<->subscriber model?
Greetings.
If there are logging experts here, I beg you to look at my question on SO (carefully, there is a lot of English text).
Here I want to ask a question regarding ETW (Event Tracing for Windows from MS): is it possible to use this framework to make a client-server architecture with the ability of the server to monitor whether new clients have appeared, and, if the answer is yes, automatically register them?
Here I consider the server as a kind of message and log router.
Making a simple client-server architecture on ETW is not difficult. However, ETW still implies the creation of clients, the number and GUID of which will be known at the design and implementation stage of the code.
I need a mechanism or ideology that will allow me to implement the server as a kind of router, and have dynamically created clients.
I indicated the register<->subscriber mechanism as an example of such an implementation. For example, in some IPC libraries such a mechanism is implemented, only there is no logging there, and you create all the messages yourself.
Thank you.
Answer the question
In order to leave comments, you need to log in
Didn't find what you were looking for?
Ask your questionAsk a Question
731 491 924 answers to any question