Aiohttp improvements, feedback wanted about aws-xray-sdk-python HOT 2 CLOSED

Hi, in general the current functionality the SDK already supports for 2.x should remain functioning. Since 3.0 is released on this month, I would assume it takes some time for most of the aiohttp users to upgrade to 3.x.

But to be more specific, support of aiohttp includes two parts: middleware and client. The SDK right now only provides a aiohttp middleware but it doesn't provide patch code for the client. So you can implement a whole 3.x support with new middleware, client/config, or you can just do the client/config and stick with the 2.x middleware for a while. But since 3.0 is already out the client support is not required to work with 2.x (someone else can backfill it).

For TraceConfig I think the naming is too general if your intention is just to carry enough information to inject trace header to the outbound http call. Could you check module TraceHeader to see if it fits your needs?

Also for client support it involves two things: one is to inject trace header to the call, the other is to capture this call as a subsegment. You can check the requests patcher to see how a call made via requests is captured and at the meantime has trace header injected: https://github.com/aws/aws-xray-sdk-python/blob/master/aws_xray_sdk/ext/requests/patch.py

Please let me know your thoughts and I'm happy to review your PR and merge it as soon as possible.

from aws-xray-sdk-python.

Close this since I believe we reached an agreement for doing client support only for 3.x for now.

from aws-xray-sdk-python.