In order to implement the end user and Gateway-daemon communications, we need to examine and make some decisions on several operational aspects of the daemon – how it's going to work, how data gets sent and received, and how that data is acted upon. In this chapter, we'll examine that in detail, and write code to implement processes based on those decisions.
The chapter covers the following topics:
- Defining what the data structure (messages) being sent back and forth looks like, and what it needs to provide, including a signed-message implementation that should work no matter what mechanism is used to send the data
- Examining two fundamental options for sending and receiving data: message queues and web services
- How messages will be handled, independently of the transmission mechanism
- The basic structures needed to implement...