Skip to content

adding compress mode and checksum, as also split of symbol #59

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

Draft
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

jryannel
Copy link
Contributor

Closes #58
Closes #57

📑 Description

  • Compress mode integers are send as identifiers instead of strings.
  • Checksum is send during LINK to ensure same objects are on both sides
  • Symbol IDs are split into ObjectID and MemberID to remove need of split/join on client/server side.

[ PROPERTY_CHANGE, "org.demos.Echo", "message", "foo"]
// 1 is the object id of "org.demos.Echo"
// 2 is the member id of "message"
[ PROPERTY_CHANGE, 1, 2, "foo"]
Copy link
Contributor

@w4bremer w4bremer Sep 14, 2023

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just to clarify this, will it be really integers or will it be integers wrapped in strings?
[ PROPERTY_CHANGE, 1, 2, "foo"] or [ PROPERTY_CHANGE, "1", "2", "foo"]

Depending on the answer we should also adapt the protocol to use integer based functions params.
Otherwise we can just use one method for both modes.

[ LINK, 1, CHECKSUM ]
```

There is no handshake messages, to ensure both client and services are in compress mode, this needs to be ensured during the deployment. If the client and service are not in the same mode, the link will fail, as the object identifier will not match.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Would it be much work to extend the link message to also sync the mode?
Bit more work now, but less headache during deployment because there would be a clear error message.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Exchanging the protocol version would also help reduce problems.

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

Successfully merging this pull request may close these issues.

[FEAT]: ObjectLink Spec: Send symbol as two parts (e.g. objectId and memberId) [FEAT]: ObjectLink Spec: Add checksum to init message from object link
2 participants