|
Noam Weissman wrote:
First
of all the code is still in development and secondly you
need lots of RAM.
That "lots of RAM" is a limitation of TLS, not a limitation of mbed
TLS or how lwIP uses it.
That code is still not finished though. And I have to come up with
RAM/ROM numbers once it is finished...
Anyway, for devices where HTTPS is only one out of many services,
that usage is far from ideal as it encrypts/decrypts data in the
tcpip_thread. And during potentially slow/long encrypt/decrypt
phases, nothing else can be done in lwIP (e.g. no packet processing,
no ping, no ACKs...). A socket or netconn-based server might be a
better idea for some...
Simon
|