You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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?
The text was updated successfully, but these errors were encountered:
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)
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:
Open issue: what would actually be in this preset?
The text was updated successfully, but these errors were encountered: