like embedded systems and servers. Web Services can be very flexible and
composable, and discovery is already specified, however, this also comes at a
cost: web services are enclosed in SOAP, which is enclosed in HTTP, which is
-transported over TCP, which introduces very much overhead, except with SOAP
+transported over TCP, which introduces very much overhead, especially with SOAP
being based on verbose XML. IPv6 support is only partially implemented.
For communication, standard APIs can be used.
which comes with protocol overhead and increased code size. However Klauck and
Kirsche show that with good optimization (in the code as well as in the
procotol), a complete stack can be implemented in 12 kByte of ROM, which leaves
-enough space for other applications to build onto it. As compared to Web
+enough space for other applications to be built onto it. As compared to Web
Services, Chatty Things are probably not as flexible, but they have less
overhead, even when using XML, while MQTT and CoAP provide less flexibility for
-future enhancement, therefore less protocol overhead and easier parsing.
+future enhancement, but less protocol overhead and easier parsing.
With TCP, mDNS, DNS-SD and XMPP as foundation, the proposed architecture builds
on reliable and established standards, which allows it to reuse Chatty Things in
(Serverless Messaging). If this gap can be closed, or a different way for topic
filtering in distributed networks is found, the server can be
eliminated and what remains is truly distributed network without the need for
-any central infrastructure, therefore eliminating every single point of failure
+any central infrastructure, therefore eliminating most single points of failure
in the system.
It is always hard to trade flexibility and accessibility for efficiency. The