Abstract: Systems and methods for viewing media content in instant messaging are provided. In an embodiment, a first IM server that manages instant messaging of a first IM client receives a chat message having a media address from a second IM client whose instant messaging is managed by a second IM server. A first media recognizer associated with the first IM server recognizes the media address in the chat message. In response to the recognition, the first IM server provides the chat message and a media instruction to the first IM client. In another embodiment, the first IM server obtains media associated with the recognized media address and provides the chat message and the obtained media to the first IM client. In a further embodiment, a system for viewing media content based on presence information in instant messaging is provided.

Abstract: Providing a framework for developing, deploying and managing sophisticated mobile solutions, with a simple Web-like programming model that integrates with existing enterprise components. Mobile applications may consist of a data model definition, user interface templates, a client side controller, which includes scripts that define actions, and, on the server side, a collection of conduits, which describe how to mediate between the data model and the enterprise. In one embodiment, the occasionally-connected application server assumes that data used by mobile applications is persistently stored and managed by external systems. The occasionally-connected data model can be a metadata description of the mobile application's anticipated usage of this data, and be optimized to enable the efficient traversal and synchronization of this data between occasionally connected devices and external systems.

Abstract: Systems and methods for viewing media content in instant messaging are provided. In an embodiment, a first IM server that manages instant messaging of a first IM client receives a chat message having a media address from a second IM client whose instant messaging is managed by a second IM server. A first media recognizer associated with the first IM server recognizes the media address in the chat message. In response to the recognition, the first IM server provides the chat message and a media instruction to the first IM client. In another embodiment, the first IM server obtains media associated with the recognized media address and provides the chat message and the obtained media to the first IM client. In a further embodiment, a system for viewing media content based on presence information in instant messaging is provided.

Abstract: A contact list search with autocomplete is described. The contact list search searches on all contact information fields, including name, email, address, company, and so forth. The search results are updated on the fly as additional characters are entered to form new query strings. When a contact is selected from the results, a profile for a contact is displayed, including text boxes for editing the profile.

Abstract: Providing a framework for developing, deploying and managing sophisticated mobile solutions, with a simple Web-like programming model that integrates with existing enterprise components. Mobile applications may consist of a data model definition, user interface templates, a client side controller, which includes scripts that define actions, and, on the server side, a collection of conduits, which describe how to mediate between the data model and the enterprise. In one embodiment, the occasionally-connected application server assumes that data used by mobile applications is persistently stored and managed by external systems. The occasionally-connected data model can be a metadata description of the mobile application's anticipated usage of this data, and be optimized to enable the efficient traversal and synchronization of this data between occasionally connected devices and external systems.

Abstract: Providing a framework for developing, deploying and managing sophisticated mobile solutions, with a simple Web-like programming model that integrates with existing enterprise components. Mobile applications may consist of a data model definition, user interface templates, a client side controller, which includes scripts that define actions, and, on the server side, a collection of conduits, which describe how to mediate between the data model and the enterprise. In one embodiment, the occasionally-connected application server assumes that data used by mobile applications is persistently stored and managed by external systems. The occasionally-connected data model can be a metadata description of the mobile application's anticipated usage of this data, and be optimized to enable the efficient traversal and synchronization of this data between occasionally connected devices and external systems.

Abstract: Providing a framework for developing, deploying and managing sophisticated mobile solutions, with a simple Web-like programming model that integrates with existing enterprise components. Mobile applications may consist of a data model definition, user interface templates, a client side controller, which includes scripts that define actions, and, on the server side, a collection of conduits, which describe how to mediate between the data model and the enterprise. In one embodiment, the occasionally-connected application server assumes that data used by mobile applications is persistently stored and managed by external systems. The occasionally-connected data model can be a metadata description of the mobile application's anticipated usage of this data, and be optimized to enable the efficient traversal and synchronization of this data between occasionally connected devices and external systems.

Abstract: Providing a framework for developing, deploying and managing sophisticated mobile solutions, with a simple Web-like programming model that integrates with existing enterprise components. Mobile applications may consist of a data model definition, user interface templates, a client side controller, which includes scripts that define actions, and, on the server side, a collection of conduits, which describe how to mediate between the data model and the enterprise. In one embodiment, the occasionally-connected application server assumes that data used by mobile applications is persistently stored and managed by external systems. The occasionally-connected data model can be a metadata description of the mobile application's anticipated usage of this data, and be optimized to enable the efficient traversal and synchronization of this data between occasionally connected devices and external systems.

Abstract: Providing a framework for developing, deploying and managing sophisticated mobile solutions, with a simple Web-like programming model that integrates with existing enterprise components. Mobile applications may consist of a data model definition, user interface templates, a client side controller, which includes scripts that define actions, and, on the server side, a collection of conduits, which describe how to mediate between the data model and the enterprise. In one embodiment, the occasionally-connected application server assumes that data used by mobile applications is persistently stored and managed by external systems. The occasionally-connected data model can be a metadata description of the mobile application's anticipated usage of this data, and be optimized to enable the efficient traversal and synchronization of this data between occasionally connected devices and external systems.

Abstract: Providing a framework for developing, deploying and managing sophisticated mobile solutions, with a simple Web-like programming model that integrates with existing enterprise components. Mobile applications may consist of a data model definition, user interface templates, a client side controller, which includes scripts that define actions, and, on the server side, a collection of conduits, which describe how to mediate between the data model and the enterprise. In one embodiment, the occasionally-connected application server assumes that data used by mobile applications is persistently stored and managed by external systems. The occasionally-connected data model can be a metadata description of the mobile application's anticipated usage of this data, and be optimized to enable the efficient traversal and synchronization of this data between occasionally connected devices and external systems.

Abstract: Providing a framework for developing, deploying and managing sophisticated mobile solutions, with a simple Web-like programming model that integrates with existing enterprise components. Mobile applications may consist of a data model definition, user interface templates, a client side controller, which includes scripts that define actions, and, on the server side, a collection of conduits, which describe how to mediate between the data model and the enterprise. In one embodiment, the occasionally-connected application server assumes that data used by mobile applications is persistently stored and managed by external systems. The occasionally-connected data model can be a metadata description of the mobile application's anticipated usage of this data, and be optimized to enable the efficient traversal and synchronization of this data between occasionally connected devices and external systems.

Abstract: A system is provided for manipulating data representation language based-objects in a native programming language environment. In one embodiment, the system is used to map data objects of the data representation language to corresponding objects within the native programming language and vice versa. In one embodiment, the system is equipped to receive a mapping definition mapping selected elements of a data representation language, such as an XML data structure, to selected objects of a programming language, such as ECMAScript. The system is further equipped to determine whether the mapping definition comprises one or more definitional statements expressed with data representation language oriented language elements of a programming language.

Abstract: A debugging proxy can be used to manage communication between a client and a debugger or debugging component. A debugging protocol can be used by the debugging proxy to facilitate communication management. A debugging protocol can provide for asynchronous messaging, and can allow for the communication of large grain messages. A debugging protocol can also implement a priority scheme that can be used to process messages between a client and a debugger based upon a priority assigned to each message.

Abstract: A tip clearance control device for a gas turbine engine having a shroud surrounding a stage of rotor blades. The tip clearance control device comprises a one-piece split ring having opposed overlapping end portions. The split ring is directly supported onto the inner surface of the shroud and is adapted to automatically adjust for thermal growth of the shroud during engine operation.