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
While we are trying to move towards GA on the callback protocol (still in preview) we made few changes to the protocol.
Current changes*:
router should specify maximum supported callback protocol version in all their messages
subgraphs should specify their callback protocol version (in headers) in all their messages
drop heartbeat message in favor of simpler check message (i.e. send heartbeats per each subscription)
heartbeat message required grouping subscription IDs per calling router without providing an easy way to group it (i.e. subgraphs would have to parse callback URLs to group heartbeats) which is error prone.**
This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.
For general questions, we recommend using StackOverflow or our discord server.
While we are trying to move towards GA on the callback protocol (still in preview) we made few changes to the protocol.
Current changes*:
heartbeat
message in favor of simplercheck
message (i.e. send heartbeats per each subscription)heartbeat
message required grouping subscription IDs per calling router without providing an easy way to group it (i.e. subgraphs would have to parse callback URLs to group heartbeats) which is error prone.**See: apollographql/router#3884
*additional changes may be necessary as we finalize the protocol
**we may revisit this optimization in the future callback protocol versions
The text was updated successfully, but these errors were encountered: