The service behaviour shall be in accordance with the patterns detailed in the Message Exchange Patterns: Identification Guidelines. The typical service behaviour, is:
- The service consumer subscribes to the service
- The service sends the latest METAR/SPECIs to subscribers when they are available and match their subscription. The interfaces have different behaviour. A combination of an AMQP 1.0 implementation and an OGC implementation shall be used for the basic behaviour.The typical behaviour for PUBLISH_SUBSCRIBE means that:
- The subscription is handled by either:
- a request-reply implementation (see IWXXM METAR-SPECI Subscription and Request Service Subscription Interface) or
- an email request to the service provider.
- The distribution of the messages is handled by an AMQP 1.0 implementation (see IWXXM METAR-SPECI Subscription and Request Service Distribution Interface).
- The typical behaviour for REQUEST_REPLY (as used in IWXXM METAR-SPECI Subscription and Request Service Request Interface) is as follows:
- Synchronous Request/Reply: The request message is sent from the service consumer to the service
- The service consumer remains blocked while awaiting the reply
- The service remains blocked while processing the reply
- The METAR-SPECI, the reply message, is sent from the service to the service consumer.