earlier i thought that tls cannot use async tcp, but it actually turns out that if tls is enabled, tcp async capability has to be turned off and is thus lost:
Note: Using TLS over asynch TCP is not supported at the moment. If you use TLS you have to disable asynch TCP!
if it is not possible to make tls use non-async tcp at the same time when async tcp is enabled for non-tls tcp transport, then my opinion is that we should wait that tls can use async tcp before sr is released.
-- juha
Juha Heinanen schrieb:
earlier i thought that tls cannot use async tcp, but it actually turns out that if tls is enabled, tcp async capability has to be turned off and is thus lost:
Note: Using TLS over asynch TCP is not supported at the moment. If you use TLS you have to disable asynch TCP!
if it is not possible to make tls use non-async tcp at the same time when async tcp is enabled for non-tls tcp transport, then my opinion is that we should wait that tls can use async tcp before sr is released.
IMO this depends on when Andrei (or somebdy else) will find some time to implement it.
klaus
Klaus Darilion writes:
IMO this depends on when Andrei (or somebdy else) will find some time to implement it.
sure, but my point was that it may not make sense to release sr at all if enabling tls means disabling async tcp, because then added value of sr as compared to k may not be big enough.
-- juha
Juha Heinanen schrieb:
Klaus Darilion writes:
IMO this depends on when Andrei (or somebdy else) will find some time to implement it.
sure, but my point was that it may not make sense to release sr at all if enabling tls means disabling async tcp, because then added value of sr as compared to k may not be big enough.
I think there are lots of other new features (modules) which justify a new release. Indeed, async TLS would be nice. But if nobody has the time to implement it very near future, I think we should release with async TLS.
regards klaus
-
jh＠tutpro.com -
Klaus Darilion