Managing Cross-Cutting QoS Issues in MULTE Middleware

f existing components and middleware entities. This must also be true for components that encapsulate resources, i.e., APIs to network services. In this position paper, we outline how we handle QoS management issues at application level, middleware level, and resource level, i.e., network and operating system (OS) to approach these problems. The main programming concepts for multimedia provided by the MULTE-ORB are explicit stream bindings, stream interfaces, flows, and associated type checking rules [1]. A binding type identifies the type of stream interfaces which can participate in the binding, the roles they play, and the way behavior at the various stream interfaces are linked. A stream interface consists of a collection of source and/or sink media flows. The binding framework defines a number of entities involved in the binding. A binding factory (BF) is a distributed entity responsible for the creation of bindings of a certain type. Existing bindings can be reconfigured by a b