On 05/16/2016 09:31 PM, Grant Edwards wrote:
On 2016-05-16, jmp <jeanmic...@sequans.com> wrote:
Have you considered upgrading the device with a recent CPU ? Or is it
completely out of the picture ?
Not an option. We have to continue to support devices that are in the
field. The newer models that are coming out now run at 133MHz instead
of 44MHz, and page load times for https still aren't much better.
That being said, your first idea seems also a good lead, have your
server refuse more than one connection.
Just got to figure out how to try it out without wasting a lot of time
reverse-engineering the web server. Hence a Python prototype. :)
I don't have time to read the whole thread but if I got it right, the
main CPU consuming part is the crypto.
Why not drop the https part an support only http ?
Is is a device that needs to be accessed in untrusted networks ? Sorry
for asking the obvious :o)
jm
--
https://mail.python.org/mailman/listinfo/python-list
