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

Proposal: proto for stream "presets" #17

Open
Ostrzyciel opened this issue Dec 30, 2024 · 2 comments
Open

Proposal: proto for stream "presets" #17

Ostrzyciel opened this issue Dec 30, 2024 · 2 comments
Labels
new protocol feature Discussion about a new feature in the Jelly protocol

Comments

@Ostrzyciel
Copy link
Member

Follow-up of Jelly-RDF/jelly-jvm#250

That issue, in short, proposes to create an "autotuner" that would automatically determine the optimal settings for a Jelly stream, including those beyond what's present in RdfStreamOptions.

It may make sense to save the result of such analysis in a proto. This could be useful in scenarios like the following:

A lightweight IoT device is producing some RDF data. The more powerful server can analyze the data and determine that there is a more optimal way to encode the same data. We could tell the IoT device to use these more optimal settings instead.

The same could be done in an offline manner. If we have a sample of the data that will be transmitted, we can analyze it and save the settings preset to the IoT device for later use.

Open issue: what would actually be in this preset?

@Ostrzyciel Ostrzyciel added the new protocol feature Discussion about a new feature in the Jelly protocol label Dec 30, 2024
@Ostrzyciel
Copy link
Member Author

There could also be a gRPC service that would take an input stream and respond with a preset that would be most appropriate for this data. It would be nice if the service also accepted some additional information about the intended channel – see: Jelly-RDF/jelly-jvm#250 (comment)

@Ostrzyciel
Copy link
Member Author

This could also include the contents of a pre-shared dictionary, if needed in that use case. See: #36

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
new protocol feature Discussion about a new feature in the Jelly protocol
Projects
None yet
Development

No branches or pull requests

1 participant