@nivaldoh I've also cleaned up the proto module and usage thereof.
The include_file bundle had the somewhat ugly side effect of producing modules like apache_beam::proto::org::apache::beam::model..., so I've added a proto.rs file which imports the handful of separate proto bundles, which produces apache_beam::proto::..., which makes more sense hierarchically. Re-exports would still highlight the original package name, so this keeps those module names brief and informative (e.g. apache_beam::proto::org::apache::beam::model::pipeline::v1 vs. apache_beam::proto::pipeline::v1).
I tried to name the module apache_beam::model (like Java and Go use, Python uses apache_beam.portability.api of which I'm not a big fan) as well, but found that having the apache_beam::proto::... prefix was more informative of the context.
Since the proto structs are so similarly named to concepts used in the SDK I've refactored usage of protos to always use a module prefix. This makes it easier to distinguish where we're dealing with protobuf messages and gRPC services.
The vN suffix makes maintenance for transitions to vN+1 a little easier and keeps the context around usage clear, so for every imported submodule from a proto package (e.g. instruction_request) I've also suffixed them with the version number (e.g. instruction_request_v1).
I've also added the corresponding version number to the external worker pool service struct name for the same reasons.

This pull request has been marked as stale due to 60 days of inactivity. It will be closed in 1 week if no further activity occurs. If you think that’s incorrect or this pull request requires a review, please simply write any comment. If closed, you can revive the PR at any time and @mention a reviewer or discuss it on the dev@beam.apache.org list. Thank you for your contributions.

This pull request has been closed due to lack of activity. If you think that is incorrect, or the pull request requires review, you can revive the PR at any time.

@sjvanrossum Could you kindly make a PR to https://github.com/laysakura/beam/ repository for these changes?

@sjvanrossum I did in laysakura#31 🙂

@laysakura That's great, thanks! I'll close this one.
I've had a busy few weeks, but will get that data channel implementation with tests over to you before EOW.