In current Relay code implementation, we only export certain fields in RelayFrame interface (up to Arg1). We would like to explore the opportunity to access/introspect Arg2 (application headers for thrift) in Relay path.
This could allow RelayHost to decide which peer to route to based on application headers, i.e. Arg2.
In current Relay code implementation, we only export certain fields in RelayFrame interface (up to Arg1). We would like to explore the opportunity to access/introspect Arg2 (application headers for thrift) in Relay path.
This could allow RelayHost to decide which peer to route to based on application headers, i.e. Arg2.