Expose additional transport details via TransportListener

[kwin]

New feature, improvement proposal

The transport listener should (optionally) get additional details about the transport. Exposing this (also in the CLI) is helpful to debug issues.

Relevant for HTTP-based transports may be

• HTTP Protocol version
• Compression algorithm (if used)
• Transfer size (compressed data size)

Increasing the log level of the underlying HTTP clients is often cumbersome, therefore it should be as easy as possible to expose those details.

[cstamas]

Not only that, I personally am always frustrated how there is no way to tell what transport Maven would use... .like mvn -v or some command should be enhanced to display it (only for HTTP maybe, as without protocol this is chicken-or-egg game). Just for HTTP we now have 4 players available... And maybe a list of available transports? As "by protocol" is hard, since the URL is not real URL, but more....

For example "file" transport supports:

• file: URIs and "naked" (w/o file:) -- would just create Path and if succeeds would use it
• symlink+file: URIs
• hardlink+file: URIs
• bundle: URIs

So best is to list existing transports...

[kwin]

Right, however details about the transport implementation should be exposed through some other means. TransportListener is really bound to a single request.

[kwin]

I created #1770 to track the issue about listing transporter details.