Skip to content

Separate protobuf from API #3

Description

@samspycher

The package parsec-interface-java currently contains the API for interacting with the wire protocol, and exposes references to protobuf classes.

Any direct references to protobuf classes should be separately packaged and hidden from external access.

Solution proposal

parsec-interface-java is built on the model of parsec-interface-rs and also named after it. This naming is somewhat confusing, since this is not an external interface, but the interface to the wire protocol.

We may introduce a parsec-api-java package to contain the actual API, and move all true external interface and parameter classes there. protobuf class interaction remains in parsec-interface-java.

Activity

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions