Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.arch.embedded > #28458

Re: "Device-to-smartphone" and "smartphone-to-device" technologies

From pozz <pozzugno@gmail.com>
Newsgroups comp.arch.embedded
Subject Re: "Device-to-smartphone" and "smartphone-to-device" technologies
Date 2018-12-14 09:17 +0100
Organization A noiseless patient Spider
Message-ID <puvovh$76j$1@dont-email.me> (permalink)
References <puk654$21p$1@dont-email.me> <m2tvjj8d8h.fsf@ip-192-168-152-57.eu-central-1.compute.internal> <putkl8$fgi$1@dont-email.me> <puu78h$4nc$1@dont-email.me>

Show all headers | View raw

Il 13/12/2018 19:09, Rob Gaddi ha scritto:
> On 12/13/18 4:51 AM, pozz wrote:
>> Il 12/12/2018 07:34, Mikko OH2HVJ ha scritto:
> 
>>> Serverless is really nice approach for cloud, but finding true
>>> experience in that field is difficult.
>>>
>>> If I were to create a small scale mobile-controlled IoT device, I 
>>> would pick
>>> -Linux SOM or ESP32 (if you've got mains power - battery is more 
>>> difficult!)
>>
>> Do you think a simple Cortex-M3 running FreeRTOS/superloop with lwip 
>> TCP/IP stack is not sufficient? This hw actually runs a HTTP server 
>> without big issues.
>>
> 
> Yeah, but it's not running HTTPS.  I think a CM3 would be woefully 
> outclassed by having to slap SSL on top of things, and if you're not 
> securing your traffic you're adding to the Internet of Crap problem.

SSL is a must, I know. And I know I can integrate mbedTLS library on top 
of lwip. This is one of a next project.

I don't know if SSL is much more slower than pure HTTP. I hope no, of 
course. Anyway, regarding about the cloud service, I could think to move 
all the web pages (.html, .java, .css, .png, ...) on a public server and 
put on only a mechanism to retrieve dynamic data (.json) from the device 
through other protocols (MQTTS or similar).

My idea is:
- the device open a connection with my *own* SERVER1, maybe MQTTS
- SERVER2 is a normal Web hosting service
- apps on smartphone are web viewer that connects to SERVER2, when the 
user wants to connect to his home
- .json HTTP requests are processed in SERVER2 and decoded in another 
HTTPS request to SERVER1 that exposes a proprietary API
- SERVER1 decodes the request from SERVER2, extract the device ID and 
type of request and transcode to MQTTS
- the answer from the device goes in the opposite direction

I hope MQTTS experience is much more fast than browsing web pages over 
HTTPS protocol. MQTTS should be a persisten connection.

I'm using now LPC1769 from NXP. I know there are MCUs with crypto 
engine: STM32F2, K6x, ...
Maybe this mess is faster on those MCUs. Any experience?

Back to comp.arch.embedded | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread

Thread

"Device-to-smartphone" and "smartphone-to-device" technologies pozz <pozzugno@gmail.com> - 2018-12-09 23:49 +0100
  Re: "Device-to-smartphone" and "smartphone-to-device" technologies Dimiter_Popoff <dp@tgi-sci.com> - 2018-12-10 12:04 +0200
    Re: "Device-to-smartphone" and "smartphone-to-device" technologies pozz <pozzugno@gmail.com> - 2018-12-10 11:33 +0100
      Re: "Device-to-smartphone" and "smartphone-to-device" technologies Dimiter_Popoff <dp@tgi-sci.com> - 2018-12-10 14:09 +0200
        Re: "Device-to-smartphone" and "smartphone-to-device" technologies pozz <pozzugno@gmail.com> - 2018-12-10 14:51 +0100
          Re: "Device-to-smartphone" and "smartphone-to-device" technologies Dimiter_Popoff <dp@tgi-sci.com> - 2018-12-10 22:50 +0200
            Re: "Device-to-smartphone" and "smartphone-to-device" technologies pozz <pozzugno@gmail.com> - 2018-12-11 14:27 +0100
              Re: "Device-to-smartphone" and "smartphone-to-device" technologies Dimiter_Popoff <dp@tgi-sci.com> - 2018-12-11 16:50 +0200
                Re: "Device-to-smartphone" and "smartphone-to-device" technologies pozz <pozzugno@gmail.com> - 2018-12-11 23:34 +0100
                Re: "Device-to-smartphone" and "smartphone-to-device" technologies Dimiter_Popoff <dp@tgi-sci.com> - 2018-12-12 02:26 +0200
  Re: "Device-to-smartphone" and "smartphone-to-device" technologies Theo <theom+news@chiark.greenend.org.uk> - 2018-12-10 14:34 +0000
    Re: "Device-to-smartphone" and "smartphone-to-device" technologies pozz <pozzugno@gmail.com> - 2018-12-10 23:05 +0100
      Re: "Device-to-smartphone" and "smartphone-to-device" technologies Theo <theom+news@chiark.greenend.org.uk> - 2018-12-11 11:58 +0000
        Re: "Device-to-smartphone" and "smartphone-to-device" technologies pozz <pozzugno@gmail.com> - 2018-12-11 14:36 +0100
  Re: "Device-to-smartphone" and "smartphone-to-device" technologies lasselangwadtchristensen@gmail.com - 2018-12-10 13:17 -0800
    Re: "Device-to-smartphone" and "smartphone-to-device" technologies pozz <pozzugno@gmail.com> - 2018-12-10 23:05 +0100
  Re: "Device-to-smartphone" and "smartphone-to-device" technologies Robert Wessel <robertwessel2@yahoo.com> - 2018-12-10 20:18 -0600
  Re: "Device-to-smartphone" and "smartphone-to-device" technologies Mikko OH2HVJ <mikko.syrjalahti@nospam.fi> - 2018-12-12 08:34 +0200
    Re: "Device-to-smartphone" and "smartphone-to-device" technologies pozz <pozzugno@gmail.com> - 2018-12-13 13:51 +0100
      Re: "Device-to-smartphone" and "smartphone-to-device" technologies Rob Gaddi <rgaddi@highlandtechnology.invalid> - 2018-12-13 10:09 -0800
        Re: "Device-to-smartphone" and "smartphone-to-device" technologies Grant Edwards <invalid@invalid.invalid> - 2018-12-13 18:59 +0000
          Re: "Device-to-smartphone" and "smartphone-to-device" technologies Rob Gaddi <rgaddi@highlandtechnology.invalid> - 2018-12-13 11:17 -0800
            [OT] Gopher Stef <stef33d@yahooI-N-V-A-L-I-D.com.invalid> - 2018-12-13 21:00 +0100
            Re: "Device-to-smartphone" and "smartphone-to-device" technologies Grant Edwards <invalid@invalid.invalid> - 2018-12-13 20:37 +0000
          Re: "Device-to-smartphone" and "smartphone-to-device" technologies Clifford Heath <no.spam@please.net> - 2018-12-14 08:12 +1100
            Re: "Device-to-smartphone" and "smartphone-to-device" technologies Grant Edwards <invalid@invalid.invalid> - 2018-12-13 21:46 +0000
        Re: "Device-to-smartphone" and "smartphone-to-device" technologies pozz <pozzugno@gmail.com> - 2018-12-14 09:17 +0100
          Re: "Device-to-smartphone" and "smartphone-to-device" technologies Grant Edwards <invalid@invalid.invalid> - 2018-12-14 15:18 +0000
      Re: "Device-to-smartphone" and "smartphone-to-device" technologies Mikko OH2HVJ <mikko.syrjalahti@nospam.fi> - 2018-12-15 18:20 +0200

csiph-web