[receiver/windowsservice] Added receiver scrape wireframe #39387
Conversation
This file contains hidden or 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 PR was marked stale due to lack of activity. It will be closed in 14 days. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
This PR adds the outline for the scraping functionality to the Windows Service receiver. This outlines the intended structure including how the receiver will access the win32 api and serialize the results. The actual implementation details will be submitted in a separate PR once the approach and framework is agreed upon.
The primary motivation for breaking the PRs up like this is to prevent scope creep and keep code light and easy to review.
Link to tracking issue
Fixes 38619
Testing
No testing required at this point.
Documentation
README.md included as well as scratch notes on the components.