The one implementation: the library's request layer, so the analytics host's
rules and the transport profile apply as for every request. The host comes
from the analytics policy of the session's lifecycle scope. One attempt, no
error, no retry timer here: a non-2xx answer is an http failure carrying its
status, and a request that produced no answer is a transport failure
carrying the request layer's error.
An upload a platform channel sends on another of the app's stacks names its
client profile: the request goes through that profile of the transport, which
writes the stack's framing and connection headers around the caller's list,
and a body of writes goes as the stack writes it.
The one implementation: the library's request layer, so the analytics host's rules and the transport profile apply as for every request. The host comes from the analytics policy of the session's lifecycle scope. One attempt, no error, no retry timer here: a non-2xx answer is an
httpfailure carrying its status, and a request that produced no answer is atransportfailure carrying the request layer's error.An upload a platform channel sends on another of the app's stacks names its client profile: the request goes through that profile of the transport, which writes the stack's framing and connection headers around the caller's list, and a body of writes goes as the stack writes it.