Should I develop version 3.0? #1
Unanswered
mixaisealx
asked this question in
Q&A
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I have an idea for version 3.
In this version, I would like to add hooks for data packets.
Thanks to hooks, if necessary, the service will be able to configure the interception of a data packet before this packet enters the general queue.
As a result, it turns out that there is a queue of 2 stages, where the first is processing by a hook (if any), and the second is processing by other services (non-hooks).
Why do you need hooks?
Basically as a crutch that will allow some service to wedge itself into the package processing chain without making changes to other services.
It can also be useful for monitoring traffic between services. For example, to display the progress of a task to the user.
I also considered applying sorting (with lexicographic comparison) to hook IDs to create a queue of hooks.
So far, I have doubts about the need for a queue of hooks.
Now I'm not sure about the need for version 3. In fact, the implementation of the above is not so long as writing the documentation for all this later. Now I don't see much point in wasting time on this.
What about version 3 do you think? Do this version is need, for example, for you?
Beta Was this translation helpful? Give feedback.
All reactions