Persistent and/or Parallel Connections

[sarogersz]

I don't see any mention of persistent or parallel connections in the documentation for AsyncHTTPRequest_Generic. I would like to understand what are the fastest and most efficient methods of use when using the library with http triggering events that overlap in the period between request and response. Is it necessary to finish a prior request/response cycle before starting another?

[khoih-prog]

Thanks for your interest in the library.

I would like to understand what are the fastest and most efficient methods of use when using the library with http triggering events that overlap in the period between request and response. Is it necessary to finish a prior request/response cycle before starting another?

I'm afraid nobody has spent much time on this or similar libraries to measure, investigate and have answer to your special questions and use-case.

I'd appreciate if you can investigate, then post the results here to help everybody, including me.

Thanks and Regards,

[sarogersz]

Thanks for the response. I am working on using the library and can get by without making overlapping requests, but I can try it sometime and post what I find out. Shouldn’t be too hard to try. I would like to understand this library better. It could be quite useful in making code efficient when using HTTP. Stephen From: Khoi Hoang ***@***.***> Sent: Wednesday, November 17, 2021 3:42 PM To: khoih-prog/AsyncHTTPRequest_Generic ***@***.***> Cc: Stephen Rogers ***@***.***>; Author ***@***.***> Subject: Re: [khoih-prog/AsyncHTTPRequest_Generic] Persistent and/or Parallel Connections (Discussion #24) Thanks for your interest in the library. I would like to understand what are the fastest and most efficient methods of use when using the library with http triggering events that overlap in the period between request and response. Is it necessary to finish a prior request/response cycle before starting another? I'm afraid nobody has spent much time on this or similar libraries to measure, investigate and have answer to your special questions and use-case. I'd appreciate if you can investigate, then post the results here to help everybody, including me. Thanks and Regards, — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub<#24 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ADI6ON4HRTOMNNSMMUM5PCDUMQ4S5ANCNFSM5H52I66Q>. Triage notifications on the go with GitHub Mobile for iOS<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.

[sarogersz]

Looking at the example code and headers, it appears that the library can only handle sequential requests. Adding this would be a potentially significant step up in complexity, so in keeping with the idea that AsyncHTTPRequest_Generic is a "simple HTTP layer on top of the ESPAsyncTCP/AsyncTCP/STM32 AsyncTCP library to facilitate REST communication from a Client to a Server" I wouldn't expexct that this is a current or planned future capability.