This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision Next revision Both sides next revision | ||
|
blog [2013/08/14 13:49] jap [WebSocket connectivity for Embedded [2013-08-14]] |
blog [2013/08/14 13:50] jap [WebSocket connectivity for Embedded [2013-08-14]] |
||
|---|---|---|---|
| Line 29: | Line 29: | ||
| Different WebSocket architecture options | Different WebSocket architecture options | ||
| - | {{:new-web-architectures.png|}}\\ | + | {{:new-web-architectures.png?600|}}\\ |
| //Different WebSocket architecture options// | //Different WebSocket architecture options// | ||
| - | 1. Integrated - Both server and application logic resides in the same hardware. Stand-alone all-in-one solution. | + | 1. Integrated - Both server and application logic resides in the same hardware. Stand-alone all-in-one solution.\\ |
| - | 2. Pre-loaded – HTML/JS code is pre-loaded in client side, sort of Apps approach. Most lightweight. | + | 2. Pre-loaded – HTML/JS code is pre-loaded in client side, sort of Apps approach. Most lightweight.\\ |
| - | 3. Cloud wed – Web service is located in cloud, and data is exchanged directly with embedded device. Easy deployment of new UI features. | + | 3. Cloud wed – Web service is located in cloud, and data is exchanged directly with embedded device. Easy deployment of new UI features.\\ |
| 4. Cloud hub – All traffic is routed through cloud. Access through firewalls, and in case of mobile and non-static IP end-points. | 4. Cloud hub – All traffic is routed through cloud. Access through firewalls, and in case of mobile and non-static IP end-points. | ||