A CA Is a Provider of Services
A CA exists for a reason. It provides the interface between the IBA fabric and back-end logic designed to provide one or more types of services to other entities. In this context, it can be thought of as a Server. This concept breeds a series of questions:
How do other entities (CAs acting as Clients, so to speak) issue requests to a CA? The answer is: by passing messages to it.
How does the CA supply the results back to the client CA? The answer is: by sending it messages.
How are messages passed between the two? As we already know, messages are exchanged using QPs within the two CAs.
If a CA provides more than one type of service to its clients, then it probably provides each specific type of service through a specific ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access