SNIP_CLASSIC_COM_FIGURE_Figure_6_1

Figure 6.1: Auto Updating of Proxy Instance Explanation of figure 6.1: • T0: The service consumer may successfully call a service method of that proxy (and GetSubscriptionState() on subscribed events will return kSubscribed according to 6.2.3.2). • T1: The service instance goes down, correctly notified via service discovery . • T2: A call of a service method on that proxy will lead to a checked exception (ara::com::ServiceNotAvailableException), since the targeted service instance of the call does not exist anymore. Correspondingly GetSubscriptionState() on any subscribed event will return kSubscriptionPending (see also 6.2.3.2) at this point even if the event has been successfully subscribed (kSubscribed) before. • T3: The service instance comes up again, notified via service discovery infrastructure. The Communication Management at the proxy side will be notified and will silently update the proxy object instance with a possibly changed transport layer addressing information. This is illustrated in the figure with transport layer part of the proxy , which changed the color from blue to rose. The Binding implementer hint part below discusses this topic more detailed. • T4: Consequently service method calls on that proxy instance will succeed again and GetSubscriptionState() on events which the service consumer had subscribed before, will return kSubscribed again. This convenience behavior of a proxy instance saves the implementer of a service consumer from either: