Abstract: A method for sharing a video clip in real time, comprising the following steps: S1: when finding an interesting clip when watching a video by a viewer, directly selecting to share the clip in a playing interface; S2: sending a request to a video sharing service system by using a current moment as an end moment by a player; S3: accepting the request sent by the player and returning a playable address including a sharing number by the video sharing service system; S4: sending a sharing request to a social platform by the player, wherein the sharing request comprises the playable address comprising the sharing number that is returned in S3; S5: processing the sharing request in step S4 while notifying a person with whom a message is shared of a message by the social platform; and S6: accessing the playable address comprising the sharing number by the person with whom a message is shared.

Abstract: The technique introduced here includes a uniform customization system, which can support the customization of multiple software applications simultaneously. Customization data of a software application can be developed separately from the development of the application. The customization data is then stored, via the uniform customization system, into a customization storage. When the software application is executed, the software application retrieves, from the storage, the values of the customization data via the uniform customization system. The uniform customization system outputs the retrieved customization data indicating the current working context of a user, which may be used by the user to locate customization options in a customization user interface of the software application, for customizing functions performed in the current working context.

Abstract: A method for sharing a video clip in real time, comprising the following steps: S1: when finding an interesting clip when watching a video by a viewer, directly selecting to share the clip in a playing interface; S2: sending a request to a video sharing service system by using a current moment as an end moment by a player; S3: accepting the request sent by the player and returning a playable address including a sharing number by the video sharing service system; S4: sending a sharing request to a social platform by the player, wherein the sharing request comprises the playable address comprising the sharing number that is returned in S3; S5: processing the sharing request in step S4 while notifying a person with whom a message is shared of a message by the social platform; and S6: accessing the playable address comprising the sharing number by the person with whom a message is shared.

Abstract: Techniques for extended enterprise connector framework are described herein. According to one embodiment, a Java proxy is generated in a form of Java beans at a Web server as a mid-layer, using an enterprise connector. The enterprise connector provides object oriented classes that encapsulate specific function calls of a Java connector which represents a set of proprietary APIs (application programming interfaces) to access RFC modules of a backend enterprise system. A JavaScript proxy is generated for a frontend client that communicates with the Web server over the Web using a DWR (direct Web remoting) mechanism to allow the JavaScript proxy to directly access the Java proxy of the mid-layer via an AJAX (asynchronous Java and extensible markup language or XML) communication mechanism, where the JavaScript is invoked by a Web application of the frontend client at runtime. Other methods and apparatuses are also described.

Abstract: The technique introduced here includes a uniform customization system, which can support the customization of multiple software applications simultaneously. Customization data of a software application can be developed separately from the development of the application. The customization data is then stored, via the uniform customization system, into a customization storage. When the software application is executed, the software application retrieves, from the storage, the values of the customization data via the uniform customization system. The uniform customization system outputs the retrieved customization data indicating the current working context of a user, which may be used by the user to locate customization options in a customization user interface of the software application, for customizing functions performed in the current working context.

Abstract: The technique introduced here includes a uniform customization system, which can support the customization of multiple software applications simultaneously. Customization data of a software application can be developed separately from the development of the application. The customization data is then stored, via the uniform customization system, into a customization storage. When the software application is executed, the software application retrieves, from the storage, the values of the customization data via the uniform customization system. The uniform customization system outputs the retrieved customization data indicating the current working context of a user, which may be used by the user to locate customization options in a customization user interface of the software application, for customizing functions performed in the current working context.

Abstract: Methods and apparatuses for interfacing an enterprise customer with a supplier are described herein. In one embodiment, in response to a request received from an enterprise customer via a first interface (e.g., a common or universal interface) of a Web service over the Internet for a service provided by a supplier, processing logic is configured to map the request from a first format compatible with the first interface to a second format compatible with a second interface coupling with a backend system of the supplier. Processing logic invokes a method of the backend system of the supplier via the second interface (e.g., supplier specific interface) to provide the requested service to the enterprise customer using information of the mapped request. The first interface is compatible with the requesting customer and the second interface is a specific interface to the backend system of the supplier. Functionality of mapping and the second interface are maintained by the supplier.

Abstract: Techniques for organizing events via an electronic organizer are described herein. In one embodiment, an example of a process includes, but is not limited to, dynamically accessing a first event organization system over a network to retrieve a first event data representing one or more events scheduled by the first event organization system, and presenting the first event data in a second event organization system as if the first event data is scheduled by the second event organization system, wherein the first and second event organization systems are incompatible. Other methods and apparatuses are also described.

Abstract: Techniques for extended enterprise connector framework are described herein. According to one embodiment, a Java proxy is generated in a form of Java beans at a Web server as a mid-layer, using an enterprise connector. The enterprise connector provides object oriented classes that encapsulate specific function calls of a Java connector which represents a set of proprietary APIs (application programming interfaces) to access RFC modules of a backend enterprise system. A JavaScript proxy is generated for a frontend client that communicates with the Web server over the Web using a DWR (direct Web remoting) mechanism to allow the JavaScript proxy to directly access the Java proxy of the mid-layer via an AJAX (asynchronous Java and extensible markup language or XML) communication mechanism, where the JavaScript is invoked by a Web application of the frontend client at runtime. Other methods and apparatuses are also described.

Abstract: The technique introduced here includes a uniform customization system, which can support the customization of multiple software applications simultaneously. Customization data of a software application can be developed separately from the development of the application. The customization data is then stored, via the uniform customization system, into a customization storage. When the software application is executed, the software application retrieves, from the storage, the values of the customization data via the uniform customization system. The uniform customization system outputs the retrieved customization data indicating the current working context of a user, which may be used by the user to locate customization options in a customization user interface of the software application, for customizing functions performed in the current working context.

Abstract: Techniques for organizing events via an electronic organizer are described herein. In one embodiment, an example of a process includes, but is not limited to, dynamically accessing a first event organization system over a network to retrieve a first event data representing one or more events scheduled by the first event organization system, and presenting the first event data in a second event organization system as if the first event data is scheduled by the second event organization system, wherein the first and second event organization systems are incompatible. Other methods and apparatuses are also described.

Abstract: Methods and apparatuses for interfacing an enterprise customer with a supplier are described herein. In one embodiment, in response to a request received from an enterprise customer via a first interface (e.g., a common or universal interface) of a Web service over the Internet for a service provided by a supplier, processing logic is configured to map the request from a first format compatible with the first interface to a second format compatible with a second interface coupling with a backend system of the supplier. Processing logic invokes a method of the backend system of the supplier via the second interface (e.g., supplier specific interface) to provide the requested service to the enterprise customer using information of the mapped request. The first interface is compatible with the requesting customer and the second interface is a specific interface to the backend system of the supplier. Functionality of mapping and the second interface are maintained by the supplier.