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
We need to define how the protocol can evolve and how new capabilities can be defined. Ideally we would want this evolution to be non-breaking, so that interoperability between new and old versions is preserved.
This is also related to the mechanism which should be used when a particular currently defined capability is not supported by the agent or the server. Perhaps we can use the same mechanism for detection of both current and future capabilties.
The text was updated successfully, but these errors were encountered:
Resolvesopen-telemetry#7Resolvesopen-telemetry#25
This change clarifies how the protocols should work when a particular
capability is not supported. It also defines how future extensions
for the protocol capabilities will work.
Resolvesopen-telemetry#7Resolvesopen-telemetry#25
This change clarifies how the protocols should work when a particular
capability is not supported. It also defines how future extensions
for the protocol capabilities will work.
Resolves#7Resolves#25
This change clarifies how the protocols should work when a particular
capability is not supported. It also defines how future extensions
for the protocol capabilities will work.
We need to define how the protocol can evolve and how new capabilities can be defined. Ideally we would want this evolution to be non-breaking, so that interoperability between new and old versions is preserved.
This is also related to the mechanism which should be used when a particular currently defined capability is not supported by the agent or the server. Perhaps we can use the same mechanism for detection of both current and future capabilties.
The text was updated successfully, but these errors were encountered: