[new] PART-1 NamedPipeService

[cschuchardt88]

Description

What this service does, is allow communication with the node, when it is running as a windows service or systemd service. Communication between the neo-cli and node, allowing a developer to receive all, if not more information from the node.

Type of change

• Optimization (the change is only an optimization)
• Style (the change is only a code style for better maintenance or standard purpose)
• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• This change requires a documentation update

How Has This Been Tested?

Checklist:

• My code follows the style guidelines of this project
• I have performed a self-review of my code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes
• Any dependent changes have been merged and published in downstream modules

[shargon]

this plugin only send the exceptions?

[shargon]

Why we need it? maybe ping, but null?

[cschuchardt88]

If you request a Block for example. If may not be at the that height yet or doesn't exists (if you request something else). In this case we return null. Could return exception too depending on what it is.

[cschuchardt88]

In short, just for empty protocol messages. Like command GetBlockHeight

[cschuchardt88]

this plugin only send the exceptions?

Does both will send and log to Utility.Log. Reason for this is because when I create the Windows/systemd service The CLI will need to know what is happening with the node. So it can display error to user.