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

Split data model #4552

Open
mversic opened this issue May 6, 2024 · 0 comments
Open

Split data model #4552

mversic opened this issue May 6, 2024 · 0 comments
Labels
question Further information is requested

Comments

@mversic
Copy link
Contributor

mversic commented May 6, 2024

logically, there is 3 apis:

  1. client - server
  2. server - executor
  3. client - executor

4th is executor foreign functions and their payload. This one shouldn't be mixed with the previous ones. And this one doesn't have to be stabilized for the time being because it is low level and user is always required to use some of the provided macros to.

5th is iroha_schema where we could also say that schema doesn't need to be stabilized because users will always be required to use one of iroha clients but here I don't find that argument entirely convincing

Proposed changes

not sure. Let's figure out what is the scope of change needed here and if we need to do some refactoring

Motivation

structs and APIs that cannot be used by client shouldn't be accessible by the client, etc.

@mversic mversic added the question Further information is requested label May 6, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

1 participant