Disconnect between server/client(.socket).port and network.transport (TCP/UDP)

[trask]

It seems that the network.transport attribute was moved to trace-specific attributes, and the port is ambiguous if we don't know whether it was UDP or TCP

Originally posted by @Oberon00 in #244 (comment)

[trask]

It seems that the network.transport attribute was moved to trace-specific attributes

I sent #256 for this

and the port is ambiguous if we don't know whether it was UDP or TCP

@Oberon00 can you clarify if you think there's a specific change you're thinking that we should make related to this? thx

[trask]

@Oberon00 i'm not clear about this part

and the port is ambiguous if we don't know whether it was UDP or TCP

and want to make sure we're not missing something that's needed for HTTP stability, thx!

[Oberon00]

The issue I mentioned on the linked comment is resolved with your #256. Thank you! I can make another suggestion on the port specification.

EDIT: I created PR #289. We can close this issue by merging that, but even if we decide not to merge, the issue is sufficiently addressed and can be closed after we decide that.