|
From: | Noam Weissman |
Subject: | Re: [lwip-users] HTTPS support in lwip |
Date: | Wed, 17 May 2017 20:58:18 +0000 |
Simon,
If I was not clear, my apologies... lots of RAM due to the use of SSL and not LwIP
BR, Noam. From: lwip-users <lwip-users-bounces+address@hidden> on behalf of address@hidden <address@hidden>
Sent: Wednesday, May 17, 2017 9:34 PM To: Mailing list for lwIP users Subject: Re: [lwip-users] HTTPS support in lwip Noam Weissman wrote:
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 |
[Prev in Thread] | Current Thread | [Next in Thread] |