Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Complexity of the design regarding path types #145

Open
juagargi opened this issue Dec 1, 2022 · 0 comments
Open

Complexity of the design regarding path types #145

juagargi opened this issue Dec 1, 2022 · 0 comments

Comments

@juagargi
Copy link
Member

juagargi commented Dec 1, 2022

There exists a number of slayers paths that are necessary to express the different types of paths that the implementation supports.

We also have the snet.DataplanePath interface that is needed to synchronize values between the SCION header and the particular path header.

We also have the snet.RawPath that has the unprocessed path received in the packet. Why though?

We also have the snet.RawReplyPath, because RawPath cannot be reversed?

We should get rid of all but the slayers ones, and if we want to hide the particularities of the types behind a facade, a type that just delegates the needed functionality to the underlying slayers path.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant