Castrated performance of AT^SISW ? Surely this can't be the only way to use HTTP ? | Telit Cinterion IoT Developer Community
February 9, 2019 - 8:22pm, 1944 views
Is it really true that the only way to send data to the HTTP service is using the castrated performance of the AT^SISW command? This only allows 1460 bytes per command and means that uploads of megabytes of data takes magnitudes more time to transmit to the Gemalto module than it does to go OTA.
This seems a completely ridiculous situation for such an advanced module. Surely there must be a way to use a feature such as AT^SIST to bulk-stream data in to the HTTP service? As it is, I'm faced with the situation of having to use transparent sockets and implement all of HTTP myself in my external code, which seems crazy.
I have actually tried fairly hard (tried lots of different ways) to see if AT^SIST can be used instead of AT^SISW for HTTP connections but everything I've tried fails. I am very, very disappointed.