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
In our implementation, we only set the TaxjarApi object properties upon construction, and beyond that, we mostly just perform a bunch of calls to TaxForOrderAsync(). Does anyone happen to know if it's safe enough for usage scenarios like this to create a single instance of the TaxjarApi object and perform concurrent calls to TaxForOrderAsync()?
The most notable risk I can surmise might be related to the usage of the RestSharp client library prior to version 110. I haven't spent much time tracing through the RestSharp source code, but it seems the biggest concern with versions between 108 and 110 might be scenarios where consumers are making changes to the RestSharp ParametersCollections, and that doesn't seem to be the case with the TaxJar implementation. Still, our implementation is mission critical enough that I'm hesitant to share an instance of a TaxjarApi object between threads until I've heard some casual confirmation that it's probably okay to call TaxForOrderAsync() concurrently.
The text was updated successfully, but these errors were encountered:
In our implementation, we only set the TaxjarApi object properties upon construction, and beyond that, we mostly just perform a bunch of calls to TaxForOrderAsync(). Does anyone happen to know if it's safe enough for usage scenarios like this to create a single instance of the TaxjarApi object and perform concurrent calls to TaxForOrderAsync()?
The most notable risk I can surmise might be related to the usage of the RestSharp client library prior to version 110. I haven't spent much time tracing through the RestSharp source code, but it seems the biggest concern with versions between 108 and 110 might be scenarios where consumers are making changes to the RestSharp ParametersCollections, and that doesn't seem to be the case with the TaxJar implementation. Still, our implementation is mission critical enough that I'm hesitant to share an instance of a TaxjarApi object between threads until I've heard some casual confirmation that it's probably okay to call TaxForOrderAsync() concurrently.
The text was updated successfully, but these errors were encountered: