Abstract: Event handler records, for different event handlers in different domains, are stored in an event handler orchestrator service. The event handler records identify event handlers (in various domains) that are to handle events raised in separate domains. When an event is raised, the event handler records are filtered to identify an event handler that has indicated an interest in the raised event, and an end point corresponding to the identified event handler is provided back to the calling process. The calling process then invokes the event handler for which the end point is returned.

Abstract: Event handler records, for different event handlers in different domains, are stored in an event handler orchestrator service. The event handler records identify event handlers (in various domains) that are to handle events raised in separate domains. When an event is raised, the event handler records are filtered to identify an event handler that has indicated an interest in the raised event, and an end point corresponding to the identified event handler is provided back to the calling process. The calling process then invokes the event handler for which the end point is returned.

Abstract: Event handler records, for different event handlers in different domains, are stored in an event handler orchestrator service. The event handler records identify event handlers (in various domains) that are to handle events raised in separate domains. When an event is raised, the event handler records are filtered to identify an event handler that has indicated an interest in the raised event, and an end point corresponding to the identified event handler is provided back to the calling process. The calling process then invokes the event handler for which the end point is returned.

Abstract: Event handler records, for different event handlers in different domains, are stored in an event handler orchestrator service. The event handler records identify event handlers (in various domains) that are to handle events raised in separate domains. When an event is raised, the event handler records are filtered to identify an event handler that has indicated an interest in the raised event, and an end point corresponding to the identified event handler is provided back to the calling process. The calling process then invokes the event handler for which the end point is returned.

Abstract: Systems, methods, and software technology for tracking component latency. A component tracking method records the start-times and end-times of components as they execute in furtherance of a request for a service. In addition, a dependency tracking method records the start-times and the end-times of one or more dependencies of the components, which may also be executed in furtherance of the requests. A latency of each component may be determined from its start-time and end-time, as well as the start-times and end-times of its dependencies. In some implementations, component latency may be analyzed on a per-request basis.

Abstract: An autodiscovery service for clients in an electronic messaging system is disclosed. Client devices in the system request messaging system configuration settings from an autodiscover server. Clients may derive the address of the autodiscover server from user input, such as an email address, or the address may be obtained by other means. The autodiscover server responds to the request with settings for that client. The settings requested may include addresses of electronic mail servers and other servers that provide client services. The autodiscover server may determine the settings for the client based on various criteria, including client location and user mailbox location. Third party servers may participate in the autodiscovery service, and addresses of third party servers may be included in the settings provided to the client devices.