16
edits
Difference between revisions of "Tech pages/IoT HttpOverXmpp"
Jump to navigation
Jump to search
no edit summary
(Created page with "To Be Added there are many aims in fact. But one aim is to be able to move existing applications (web applications, web services, semantic applications, etc. hosted on the web...") |
|||
| Line 1: | Line 1: | ||
= Layout= | |||
[[Tech pages/IoT_systems|Main]] Main page | |||
[[Tech pages/IoT_XepsExplained|IoT_XepsExplained]] Description of xeps and their interaction | |||
[[Tech pages/IoT_Examples|IoT_Examples]] Mashup some examples from different industries, help finding new ones | |||
[[Tech pages/IoT_Support|IoT_Support]] Here we describe who support this and related work that can help you. | |||
[[Tech pages/IoT_Interoperability|IoT_Interoperability]] How we will keep everything truly interoperable | |||
[[Tech pages/IoT_XMPP_Process|IoT_XMPP_Process]] How is the process of the xep's and interoperability interfaces managed | |||
[[Tech pages/IoT_ConstrainedDevices|IoT_ConstrainedDevices]] Going in to the world of restricted devices we need special care. | |||
[[Tech pages/IoT_LocalEnvironment|IoT_LocalEnvironment]] When dealing with home automation or a local network we need serverless or a local server configuration | |||
[[Tech pages/IoT_HttpOverXmpp|IoT_HttpOverXmpp]] This extension creates a view of webservices through the XMPP network | |||
= Introduction = | |||
To Be Added | To Be Added | ||
| Line 5: | Line 19: | ||
But one aim is to be able to move existing applications (web applications, web services, semantic applications, etc. hosted on the web) and move them into new settings (for instance hosting it at home) and be able to reuse them without having to change them or opening ports in firewalls. An example would be to access your thermostat (that has a built in web page) from your office. | But one aim is to be able to move existing applications (web applications, web services, semantic applications, etc. hosted on the web) and move them into new settings (for instance hosting it at home) and be able to reuse them without having to change them or opening ports in firewalls. An example would be to access your thermostat (that has a built in web page) from your office. | ||
Another aim is to be able to create new applications (web applications, web services, semantic applications) and be able to use them both on the web, but also safely for instance hosting them at home, and accessing them from the outside without having to code explicitly for this. It would be automatic, through the use of xmpp:// URL scheme. | Another aim is to be able to create new applications (web applications, web services, semantic applications) and be able to use them both on the web, but also safely for instance hosting them at home, and accessing them from the outside without having to code explicitly for this. It would be automatic, through the use of xmpp:// URL scheme. | ||
The only implementation required is to implement support for it in the corresponding web server (for instance open source Apache) and a browser (open source Fire Fox, Chromium, for instance), instead of having to implement peer-to-peer technology into the application itself (or all the applications themselves - thousands, tens of thousands, hundreds of thousands, millions?). | The only implementation required is to implement support for it in the corresponding web server (for instance open source Apache) and a browser (open source Fire Fox, Chromium, for instance), instead of having to implement peer-to-peer technology into the application itself (or all the applications themselves - thousands, tens of thousands, hundreds of thousands, millions?). | ||
Another aim is to extend semantic technologies from HTTP to XMPP, to be able to create more secure applications, for instance in the Internet of Things. | Another aim is to extend semantic technologies from HTTP to XMPP, to be able to create more secure applications, for instance in the Internet of Things. | ||