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
Is your feature request related to a problem? Please describe.
Create a driver in the likes of the vtls used in cURL.
The idea is that any vendor software coul be integrated inside TotalCross providing a custom settings of a structure
Describe the solution you'd like
The first step would be to become completly independent of vendoring axtls source, just creating a virtual tls driver for axtls such that it could be futurely swapped by any tls implementor. This tackles #330 and gives a way to solve to solve the issue gitlab/Totalcross/totalcross#654
Devices
All. Most importantly for those who are building their own flavored TotalCross.
Additional context
Enabling future compatibility with cipher and vendor interchange. Decoupling the VM code from the library itself.
Is your feature request related to a problem? Please describe.
Create a driver in the likes of the
vtls
used in cURL.The idea is that any vendor software coul be integrated inside TotalCross providing a custom settings of a structure
Describe the solution you'd like
The first step would be to become completly independent of vendoring axtls source, just creating a virtual tls driver for axtls such that it could be futurely swapped by any tls implementor. This tackles #330 and gives a way to solve to solve the issue gitlab/Totalcross/totalcross#654
Devices
All. Most importantly for those who are building their own flavored TotalCross.
Additional context
Enabling future compatibility with cipher and vendor interchange. Decoupling the VM code from the library itself.
This issue here does not tackle completly issue gitlab/Totalcross/totalcross#654, but opens the door for using other tls libraries available.
The text was updated successfully, but these errors were encountered: