Hi Simon, Is there a way to limit the number of concurrent HTTP connection, say to one ?
If this can be done we may be able to run HTTPS with an overhead of about 40K for SSL/TLS BR, Noam. -----Original Message----- From: lwip-users [mailto:lwip-users-bounces+noam=silrd....@nongnu.org] On Behalf Of Simon Goldschmidt Sent: Thursday, May 18, 2017 3:07 PM To: lwip-users@nongnu.org Subject: Re: [lwip-users] HTTPS support in lwip Sandeep wrote: > Could you please give me a rough figure of how much RAM it may use, > just to know whether it is viable in the above said system? The most consuming part is that TLS requires 16 kByte per direction and connection as encrypt/decrypt buffer. As modern web browsers open multiple connections (~6?), that means you need >= 192 Byte only for TLS. Of course that can be stripped down, but that's additional work to do. Simon _______________________________________________ lwip-users mailing list lwip-users@nongnu.org https://lists.nongnu.org/mailman/listinfo/lwip-users _______________________________________________ lwip-users mailing list lwip-users@nongnu.org https://lists.nongnu.org/mailman/listinfo/lwip-users
