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
Looking through the project history the decision to call out to the xmlsec1 binary made sense at the time due to the poor state of the library. However, the library looks to be in far better state now, with regular updates and a far more usable API, as well as pre-built wheels available for many architectures.
Using the library directly should offer both performance and safety benefits compared to the current setup, in addition to enabling new applications such as lambda/serverless deployments
The text was updated successfully, but these errors were encountered:
Looking through the project history the decision to call out to the xmlsec1 binary made sense at the time due to the poor state of the library. However, the library looks to be in far better state now, with regular updates and a far more usable API, as well as pre-built wheels available for many architectures.
Using the library directly should offer both performance and safety benefits compared to the current setup, in addition to enabling new applications such as lambda/serverless deployments
The text was updated successfully, but these errors were encountered: