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
It is desirable, for a number of uses within both our unity client and our .net test bed, to consolidate the entirety of the call, not necessarily the content, and some review processes object to necessity of reflection to extract the data.
It would be lovely if the ILogger interface provided one of the following solutions. All would work.
A UUID identifying the http transaction involved, allowing the evaluating stream to group the results
A single typed parameter interface call providing HTTP Command, destination URL, size, and HTTP return, or (more fancy)
A single typed parameter all with HTTP command, destination URL, payload out and back, an HTTP return.
For practical consideration for most logging schemes, the caller already has plenty of access to content, but size and disposition rom this level would be invaluable and allow direct connection to third party or n house time series logging.
A very fancy solution would provide the resolving UUID from within the RPC.
The text was updated successfully, but these errors were encountered:
It is desirable, for a number of uses within both our unity client and our .net test bed, to consolidate the entirety of the call, not necessarily the content, and some review processes object to necessity of reflection to extract the data.
It would be lovely if the ILogger interface provided one of the following solutions. All would work.
For practical consideration for most logging schemes, the caller already has plenty of access to content, but size and disposition rom this level would be invaluable and allow direct connection to third party or n house time series logging.
A very fancy solution would provide the resolving UUID from within the RPC.
The text was updated successfully, but these errors were encountered: