|
||||
|
||||
|
 |
 |
|
|
|
|
||||||||||||||||||||||||||
| Service: Indigo enables developers to fully exploit the power of service-oriented architecture. The service model is the highest level of Indigo's architecture. Developers use declarative attributes to mark up which aspects of their type (object) should form the external contract of a service and be visible to service consumers. |
| Channels: A channel is an I/O device that the service uses for sending and receiving data. This type of channel maps underlying communication mechanisms to Indigo. |
| Transport Channels: A channel is an I/O device that the service uses for sending and receiving data. Transport channels get it into the relevant format such as IPC, HTTP, or TCP. |
| Policy Engine: Enables developers and administrators to easily define policy parameters of channel usage, such as transport protocols and security parameters. |
| Channel Security: Provides cryptographic services for channels to secure the data transfer between sender and receiver. |
| Message Encoder: Encodes and decodes messages to multiple formats. |
| Communications Manager: Creates ports and channels, manages their lifetime, and enforces security policies. |
| Queuing: Queuing service based on MSMQ technology enables asynchronous guaranteed delivery of messages. |
| Eventing: Eventing enables an application to register for a specific event on a specific queue and be notified only when the event is raised (for example, when a message is received). |
| Routing: MSMQ supports dynamic routing, which allows MSMQ to dynamically select which network to use for message delivery from a pool of user-defined networks. |
| Transaction: Transactions enable multiple messages to be processed as a unit; all succeed or all fail. |
| Federation: Message-based security scheme needed for disconnected or datagram-based scenarios in which the receiver is not necessarily available at the time of transmission. Indigo supports and uses Web services standard protocols (WS-Security, WS-Federation), ensuring interoperability with other Web services platforms. |
| People and Groups: Indigo uses WinFS's unified storage model to provide a single central repository for applications, so that all collaborating applications can share the same store (instant messaging, mail clients, phone and fax applications, and so on). |
| Collaboration History: Enables storing collaboration history using a unified model. Collaboration history could include chat logs for instant-messaging applications or order history for CRM applications. |
| Real-Time Activities: Uses standard protocols such as SIP (Session Initiation Protocol) to allow real-time communication. |
| Signaling: Allows notification of events. For example, when someone logs on to IM, all his or her contacts are notified. |
