WO2011097078A1 - Widget framework, real-time service orchestration, and real-time resource aggregation - Google Patents
Widget framework, real-time service orchestration, and real-time resource aggregation Download PDFInfo
- Publication number
- WO2011097078A1 WO2011097078A1 PCT/US2011/022109 US2011022109W WO2011097078A1 WO 2011097078 A1 WO2011097078 A1 WO 2011097078A1 US 2011022109 W US2011022109 W US 2011022109W WO 2011097078 A1 WO2011097078 A1 WO 2011097078A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- call
- response
- resource
- module
- optimizations
- Prior art date
Links
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/46—Multiprogramming arrangements
- G06F9/54—Interprogram communication
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/46—Multiprogramming arrangements
- G06F9/54—Interprogram communication
- G06F9/547—Remote procedure calls [RPC]; Web services
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/60—Software deployment
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
- H04L65/10—Architectures or entities
- H04L65/1063—Application servers providing network services
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/04—Protocols specially adapted for terminals or networks with limited capabilities; specially adapted for terminal portability
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/10—Protocols in which an application is distributed across nodes in the network
- H04L67/1001—Protocols in which an application is distributed across nodes in the network for accessing one among a plurality of replicated servers
Definitions
- the present application relates generally to the technical field of optimizing server performance, and, in one specific example, to optimizing an efficiency of calls to services by components of an application running on an application server.
- a network-based marketplace that serves a large, world-wide community of users may find it beneficial to meet objectives of (1) rapidly developing, modifying, testing, or deploying a large number of server-side applications such that rapidly-changing needs of the users are met, (2) optimizing the server-side applications such that their deployment does not violate resource and performance constraints.
- the network-based marketplace may achieve its objective by employing a large-sized group of developers to code each server-side application by hand; however, such an approach may have various drawbacks, including producing applications that have a less consistent look-and-feel, take a longer time to develop, or are less efficient in terms of, for example, reuse of code, than applications produced using other approaches.
- the network-based marketplace may achieve its objectives by employing a small- sized group of developers to code applications that conform rigidly to a template; however, such an approach would also have various drawbacks, including producing applications that are more difficult to customize, consume more resources, or have slower performance than applications produced using other approaches.
- a widget may be a software component that has one or more user interfaces (UIs) and is backed by business logic (or services). That is, the widget may have a presentation layer that may be plugged in or configured to present one or more views and a logic layer that may be plugged in or configured to incorporate various data sources or services. The widget may also have a connection module that connects the presentation layer to the logic layer.
- UIs user interfaces
- business logic or services
- FIG. 1 A is a block diagram illustrating example relationships between components of an application and data sources and resources
- FIG. IB is a block diagram illustrating example relationships between the components of the application and the data sources and the resources after a call optimizer and a resource aggregator have been incorporated into the application of FIG. 1 A;
- FIG. 2A is a block diagram illustrating modules of an example embodiment of the call optimizer of FIG. IB;
- FIG. 2B is a block diagram illustrating additional modules of an example embodiment of the call optimizer of FIG. IB;
- FIG. 2C is a block diagram illustrating modules of an example embodiment of the resource aggregator of FIG. IB;
- FIG. 2D is a block diagram illustrating example modules of the widget 1 of FIG. 1A and FIG. IB;
- FIG. 3 is a block diagram of an example architecture of the metamodel framework;
- FIG. 4A is a flowchart of an example embodiment of a method of managing a lifecycle of a model definition
- FIG. 4B is a flowchart of an example method of generating an API to configure a component (e.g., a Help page) of an application;
- a component e.g., a Help page
- FIG. 5 depicts an example schema diagram of the configuration of the component of FIG. 4B
- FIG. 6 depicts an example schema corresponding to the schema diagram of FIG. 4;
- FIG. 8 depicts an example API for configuring the component that is based on the example schema of FIG. 6 or the types of FIG. 7;
- FIG. 12B is a source code listing of an example Java test client (e.g., TestClient.java);
- FIG. 12C is a Java console log associated with a running of the example HTML page and the Java test client in a web browser;
- FIG. 13B is a flowchart of an example method for aggregating resources used by the components of the application;
- FIG. 14 is an example method for designing, editing, configuring, testing, or deploying multiple versions of the application;
- the term "BizMo” includes a business module that may include user interface (UI) presentation, data/service access, including input, or configuration.
- the term “Action Input” includes input parameters for a Business Module to make an action.
- the term “BizOp” or “BizOperation” includes business operations a business module may delegate to an outside entity (e.g., a service call). A BizOp may be plugged in as a strategy into a business module.
- the term “BizMo View” includes the UI of a business module.
- the term “View Builder” includes a UI builder that can be plugged in as a strategy into a business module.
- a machine-readable storage medium comprising instructions that, when executed by one or more processors of a machine, causes the machine to perform a method to optimize the calls to the service by the components of the application running on the application server.
- the method includes receiving the first call and the second call, selecting one of multiple optimizations, the multiple optimizations including orchestrating the first call and the second call into the third call to the service; and, in response to the selecting of the orchestrating of the first call and the second call into the third call as the one of the multiple optimizations, orchestrating the first call and the second call into the third call.
- Resource 3 142 may include an aggregation of elements of resource 1 134 and resource 2 138 that application 104 uses. Resource 3 142 may not include elements of resource 1 134 or resource 2 138 that are redundant with each other.
- the incorporation of the call optimizer 116 into the application 104 may cause a number of service calls upon which application 104 relies to be reduced, and the incorporation of the resource aggregator 118 into the application 104 may cause a number of resources upon which the application 104 relies to be reduced. This optimization of service calls and aggregation of resources may improve the efficiency or performance of the application 104.
- the applying of the orchestrating of the calls may include integrating a plurality of request parameters of the first call into a plurality of request parameters of a third call, integrating a plurality of request parameters of the second call into the plurality of request parameters of the third call, making the third call, receiving a result of the third call, identifying a first part of the result as corresponding to the first call, identifying a second part of the result as corresponding to the second call, providing the first part of the result to the first one of the plurality of components as a response to the first call, or providing the second part of the result to the second one of the plurality of components as a response to the second call.
- Other ones of the multiple techniques of optimizing the calls are described below with reference to FIG. 2B.
- FIG. 2B is a block diagram illustrating additional modules of an example embodiment of the call optimizer 116 of FIG. IB.
- the call optimizer 116 may include an optimization-selection module 204, a batching module 242, a caching module 244, or an executing module 246.
- the optimization-selection module 204 may select one technique of optimizing the calls from multiple techniques of optimizing the calls.
- the multiple techniques of optimizing the calls may include providing a response to the first call or the second call from a cache, orchestrating the first call and the second call into a third call, making a batch call, executing the first call and the second call in parallel, and so on.
- FIG. 2C is a block diagram illustrating modules of an example embodiment of the resource aggregator 118 of FIG. IB.
- the resource aggregator 118 may include an identifying module 222, an aggregating module 224, or an updating module 226.
- the identifying module 222 may identify that at least a portion of a first resource of multiple resources associated with an application (e.g., application 102) is redundant with at least a portion of a second resource of the multiple resources.
- the identifying module 222 may identify that the first resource is an updated version of the second resource or that the application can use at least a portion of the first resource instead of the second resource.
- the aggregating module 224 may, in response to the identifying that at least the portion of the first resource is redundant with at least the portion of the second resource, aggregate the first resource and the second resource into a third resource.
- the third resource may include portions of the first resource and portions of the second resource that the application uses.
- the connecting module 266 may connect the presenting module 262 to the logic-implementing module 264 such that the presenting module 262 can integrate into the one or more UIs a presentation of data received from the logic-implementing module 264, including data that the logic-implementing module 264 receives through the accessing of the one or more data sources.
- applying a German (e.g., de-DE) localization to the widget 1 112 may cause text associated with the widget 1 112 to be in the German language
- applying an English as used in the United States (e.g., en-US) localization to the widget 1 112 may cause the text associated with the widget 1 112 to be in the English language.
- Each complex type may include members of the basic type or additional members, including associations (a role, a type, or a multiplicity), or attributes (simple name or value pairs).
- a role may be the name of an instance of an association.
- the multiplicity may be a single multiplicity (0, 0..1, 1), a list multiplicity (0..n, 1..n), or a map multiplicity (with strings or enumerations as keys).
- ChoiceDataDef objects that become interfaces or enumerations through the code generation process.
- FIG. 3 is a block diagram of an example architecture 300 of the metamodel framework.
- the metamodel framework may include a user 302.
- the user 302 may interact with a metadata modeling 310 component of the framework to model metadata (e.g., create type definitions, generate APIs, and so on).
- the metadata modeling 310 component may include a metadata tool or application 306 that provides a user interface to model metadata.
- the tool may create metadata or a domain model 308.
- the modeled metadata may become an input or be otherwise associated with a metadata system 320.
- the metadata system 320 may include an agent or mediation layer 314.
- the agent or mediation layer 314 may include an interpreter 312, a generator 316, or a mapper 318.
- the method 400 may include declaring 402 a type (e.g., creating a type definition that includes a reference to a type), instantiating 404 an object or structure based on the type (e.g., instantiating the type), or setting 406 data in the structure (e.g., setting a value associated with the instantiate type).
- a type e.g., creating a type definition that includes a reference to a type
- instantiating 404 an object or structure based on the type e.g., instantiating the type
- setting 406 data in the structure e.g., setting a value associated with the instantiate type.
- FIG. 5, FIG. 6, FIG. 7, and FIG. 8 provide example snapshots of source code associated with the method 450 (FIG. 4B) for generating the API for configuring the component of the application.
- FIG. 5 depicts an example schema diagram 500 of the configuration of the component.
- FIG. 6 depicts an example schema 600 corresponding to the schema diagram of FIG. 5.
- FIG. 7 depicts example types (e.g., classes) 700 that correspond to the example schema 600 of FIG. 6.
- FIG. 8 depicts an example API 800 for configuring the component that is based on the example schema 600 or the example types 700.
- the example architecture 300 of the metamodel framework may provide a Java-based model definition that enables type-safe plain-old Java object (POJO) model generation with key- value-coding (KVC) support, a generation of an XML marshaller or unmarshaller, a providing of run-time Java APIs for querying definitions for tooling, XSD or XMI (UML) generation for documentation or tooling purposes.
- POJO type-safe plain-old Java object
- KVC key- value-coding
- UML XMI
- FIG. 9 is a block diagram of an example embodiment of an architecture 900 of the resource framework.
- the resource framework may include an application layer 902, a type-specific access layer 922, a repository layer 942, a storage persistence interface 962, or various implementations 982 of storage repositories or systems.
- the application layer 902 may provide applications (e.g., ePages 904, services framework run-time 906 component, services framework run-time 908 component, or content repository run-time 912 component, with accesses to the resources at run time (e.g., through an application-level API).
- the type-specific access layer 922 may help in a translating between the application-layer 902 API and a repository-layer 942 API.
- the type-specific access layer 922 may include helpers associated with various resource types (e.g., an HTML resource access helper 924, a JavaScript resource access helper 926, a CSS resource access helper 928, a prototype resource access helper 930, a content resource access helper 932, and so on.).
- the repository layer 942 may include a repository-level API (e.g., IresourceRepository 944) to manage storage of the resources in memory (e.g., volatile memory).
- the repository-level API may be associated with a resource repository implementation 946 that supports registration of adapters to legacy resources, a serializer, or a converter. In this way, the repository-level API may support using a same referencing model across multiple owners or legacy systems.
- the repository-level API may support a definition of a repository structure (e.g., logical keys of resource).
- the repository-level API may support infoset-based persistence, leveraging fast or compact binary XML serializations; support for granular target, overrides, binding, or layering attributes; or a pluggable serializer or deserializer.
- the pluggable serializer or deserializer may not be coupled to the metamodel framework.
- the repository-level API may support a tracer to trace resource usage.
- the repository-level API may also support management of instances of data types (e.g., managed data).
- the respository-level API 944 may apply resources to type-safe KVC objects as well as generic objects.
- the repository- level may also expose definitions of objects (e.g., type declarations) to be edited (e.g., via a tool).
- the repository layer 942 may be associated with a storage persistence interface 962.
- the storage persistence interface 962 may include a persistence-manager API (e.g., IResourcePersistenceManager 964) to provide a common API to the underlying persistent (e.g., non-volatile) storage
- an example embodiment of the architecture 900 of the resource framework may include a resource repository that provides uniform API to access resources but allows for an addition of type-specific APIs, a resource persistence service that provides pluggable persistence mechanisms, or a prototype resource repository as an out-of-the-box solution from design time to run time.
- the example embodiment of the architecture 900 may extend best practices and features to most resource types, be easy or cheap to maintain or troubleshoot, or provide an easy go-to solution for most
- FIG. 10 is a block diagram of two widgets interacting with elements of an example widget framework 1000.
- a first one of the two widgets, widget 1 1012 may include step Al 1002, step A2 1004, or step A3 1006.
- Step Al 1002 may include operation 1 (OP1) 1008, operation 2 (OP2) 1010, or callback 1012.
- Step A2 1004 may include operation 3 (OP3) 1014 and callback (CB) 1018.
- Step A3 1006 may include operation 4 (OP4) 1016 and callback 1020.
- OP2 1010 may include a call to a second service.
- OP1 1008, OP2 1010, OP3 1014, and OP4 1016 may include a call to a first service, a second service, a third service, and a fourth service, respectively.
- Callback 1011 may be a function that a widget manager 1040 calls in response to an execution of the first call or the second call.
- Callback 1018 may be a callback function that the widget manager 1040 calls in response to an execution of the third call.
- Callback 1020 may be a function that the widget manager 1040 calls in response to an execution of the fourth call.
- a second one of the two widgets, widget 1024, may include step Bl 1022. Step Bl may include operation 5 (OP5) 1026, operation 6 (OP6) 1028, and callback 1030.
- OP5 1026 and OP6 1028 may include a call to a fifth service and a sixth service, respectively.
- the widget manager 1040 may manage widget 1 1012 and widget 2 1024, including their lifecycles or run-time operation.
- the widget manager 1040 may include a reference 1042 to widget 1 1012 or a reference 1044 to widget 2 1024.
- the widget manager 1040 may include references to steps within each widget.
- the widget manager 1040 may include a reference 1046 to step Al 1022 or a reference 1052 to step Bl 1022.
- the widget manager 1040 may intercept a call from a widget to a service and forward the call to a widget engine 1060.
- the widget engine 1060 may handle the processing of one or more calls by a widget.
- the widget engine 1060 may receive a reference 1062 to OP1 1008 or a reference 1064 to OP5 1026 from the widget manager 1040 (e.g., in response to an intercepting by the widget manager 1040 of a call by widget 1 1012 to OP 1 1008 or a call by widget 2 1024 to OP5 1026.
- the widget engine 1060 may include an optimizer 1066, an executor 1068, or a cache 1070.
- the optimizer 1066 may optimize the calls as discussed above with reference to FIG. 2A and FIG. 2B.
- the executor 1068 may execute the one or more calls serially or in parallel as discussed above with reference to FIG. 2B.
- FIG. 11 is a block diagram of interactions 1100 between an example developer tool 1122 for developing various versions (e.g., version 1 1162, version 2 1164, version 3 1166, or version 4 1168) of an application (e.g., the application 104 of FIG. IB) that may be associated with various respective clients of the application (e.g., mobile web browser 1152, web browser 1154, email client 1156, or other client 1158.
- the developer tool 1122 may be running on a developer machine 1102 that is communicatively coupled to the application server 1112.
- the various versions of the application may be running on the application server 1112.
- the mobile web browser 1152 may be running on a mobile device 1104, the web browser 1154 may be running on a personal computer 1106, the email client 1156 may be running on a user machine 1108, and the other client 1158 may be running on other device 1110.
- the various clients may be communicatively coupled to the application server 1112.
- the developer tool 1122 may include an editing module 1132, a simulating module 1136, or a deploying module 1138.
- the editing module 1132 may be capable of exposing the configurable attributes of a component (e.g., widget 1 112 of FIG. 2D) for editing. That is, the editing module 1132 may be capable of interfacing with the configuring module 268 of FIG. 2D (discussed above) to discover configurable attributes, or the metadata associated with the configurable attributes (e.g., metadata definitions), for editing.
- the editing module 1132 may be capable of configuring the component at run time (e.g., via rapid deployment using the deploying module 1138).
- the developer tool 1122 may include a simulating module 1136 that enables a simulation of the application (or specific components of the application or specific versions of the application) without requiring a deployment of the application.
- the simulating module 1136 may be a web browser (e.g., Firefox) extension that allows the application to run in the web browser.
- the extension may be separate from a Java virtual machine (JVM) such that the JVM does not have to run on a same machine as the web browser extension (e.g., in contrast, applets require the JVM on the machine where they are running).
- JVM Java virtual machine
- the application may interact with web pages and control browser menus.
- the simulating module 1136 may not use applets.
- the simulating module 1136 may have visibility into browser menus and web page tabs.
- the security model of the simulating module 1136 may not be as restrictive as applets (file input or output, cross-domain, etc.).
- the simulating module 1136 may be designed for highly interactive web page applications.
- the simulating module 1136 may support manipulating web pages with a Java-based Document Object Model (DOM), handling DOM events in Java (e.g., DOM events may be normalized before they get to Java; therefore browser-specific behavior of events (or event data) may be reduced), handling browser start or stop, page load or unload or tab events, changing the tools and right-click menus, receiving events from menus, persisting or accessing data at browser and simulating-module 1136 levels, sending arbitrary JavaScript to a web page, receiving back return values associated with the sending of the arbitrary DOM
- DOM Document Object Model
- JavaScript discovering, installing, or managing applications with an application manager (e.g., applications may be distributed through a standard HTTP URL), or accessing a built-in library of convenient UI features.
- the application manager may use an OSGi framework or be associated with an OSGi-provided manifest.fm options.
- the application may be a .jab file (e.g., a .jar file with an OSGi manifest.fm file and a custom install.rdf file).
- the communication between Java and the simulating module 1136 may be done with a platform- independent messaging standard (e.g., DLC).
- Components of the application server 1112 may be deployed on the developer machine 1102 or a machine more closely communicatively coupled to the developer machine 1102 than the application server 1112, such that the developer tool 1122 may communicate with the components (e.g., an element of the application server) deployed on the developer machine 1102 instead of the application server 1112.
- the simulating module 1136 may closely simulate the deployment of the application without communicating over a slower communication channel between the developer tool 1122 and the application server 1112.
- FIG. 12A is a source code listing 1200 of an example HTML page (e.g., demo.html) associated with the simulating module 1136.
- FIG. 12B is a source code listing 1220 of an example Java test client (e.g., TestClient.java).
- FIG. 12C is a Java console log 1240 associated with a running of the example HTML page and the Java test client in a web browser.
- FIG. 12D is an example user interface 1260 of the simulating module 1136 simulating a deployment of the example HTML page on the application server.
- FIG. 13 A is a flowchart of an example method 1300 of optimizing calls from the components of the application to a service.
- the method 1300 may include intercepting 1302 a first call to the service and a second call to the service, selecting 1304 a technique of optimizing the first call and the second call, or applying the selected technique of optimizing the first call and the second call.
- the techniques may include providing 1310 a response to the first call to the second call from a cache, orchestrating 1312 the first call and the second call into the third call, making 1314 a batch call, executing 1316 the first call and the second call in parallel, or applying 1318 another technique (e.g., applying a combination of the discussed techniques).
- FIG. 13B is a flowchart of an example method 1350 for aggregating resources used by the components of the application.
- the method 1350 may include detecting 1352 that a use of a first resource by a first widget is redundant with a use of a second resource by a second widget, creating 1354 a third resource that aggregates first resource and the second resource, configuring 1356 the first widget and the second widget to use the third resource, or externalizing 1358 the third resource such that a client can cache the third resource.
- FIG. 14 is an example method 1400 for designing, editing, configuring, testing, or deploying multiple versions of the application.
- the method 1400 may include receiving 1402 an application, creating 1404 an application, discovering 1406 a widget in the application, adding 1408 a widget to the application, configuring the widget 1410, simulating a deployment of the application 1412, or deploying multiple versions of the application 1414.
- ARCHITECTURE
- FIG. 15 is a network diagram depicting a client-server system 1500, within which various example embodiments may be deployed.
- a networked system 1 02 in the example forms of a network-based marketplace or other publication system, provides server-side functionality via a network 1504 (e.g., the Internet or Wide Area Network (WAN)) to one or more clients.
- FIG. 15 illustrates, for example, a web client 1506 (e.g., a browser, such as the Internet Explorer browser developed by Microsoft Corporation of Redmond,
- An Application Program Interface (API) server 1514 and a web server 1516 are coupled to, and provide programmatic and web interfaces respectively to, one or more application servers 1518.
- the application servers 1518 host one or more marketplace applications 1520 and payment applications 1522.
- the application servers 1518 are, in turn, shown to be coupled to one or more databases servers 1524 that facilitate access to one or more databases 1526.
- the marketplace applications 1520 may provide a number of marketplace functions and services to users that access the networked system 1502.
- the payment applications 1522 may likewise provide a number of payment services and functions to users.
- the payment applications 1522 may allow users to accumulate value (e.g., in a commercial currency, such as the U.S. dollar, or a proprietary currency, such as "points") in accounts, and then later redeem the accumulated value for products (e.g., goods or services) that are made available via the marketplace applications 1520. While the marketplace and payment applications 1520 and 1522 are shown in FIG. 15 to both form part of the networked system 1502, it will be appreciated that, in alternative embodiments, the payment applications 1522 may form part of a payment service that is separate and distinct from the networked system 1502.
- the system 1500 shown in FIG. 15 employs a client- server architecture
- the present disclosure is, of course, not limited to such an architecture, and could equally well find application in a distributed, or peer-to- peer, architecture system, for example.
- the various marketplace and payment applications 1520 and 1522 could also be implemented as standalone software programs, which do not necessarily have networking capabilities.
- the web client 1506 accesses the various marketplace and payment applications 1520 and 1522 via the web interface supported by the web server 1516.
- the programmatic client 1508 accesses the various services and functions provided by the marketplace and payment applications 1520 and 1522 via the programmatic interface provided by the API server 1514.
- the programmatic client 1508 may, for example, be a seller application (e.g., the TurboLister application developed by eBay Inc., of San Jose, California) to enable sellers to author and manage listings on the networked system 1502 in an off-line manner, and to perform batch-mode communications between the programmatic client 1508 and the networked system 1502.
- a seller application e.g., the TurboLister application developed by eBay Inc., of San Jose, California
- FIG. 15 also illustrates a third-party application 1528, executing on a third-party server machine 1530, as having programmatic access to the networked system 1502 via the programmatic interface provided by the API server 1514.
- the third-party application 1528 may, utilizing information retrieved from the networked system 1502, support one or more features or functions on a website hosted by the third party.
- the third-party website may, for example, provide one or more promotional, marketplace or payment functions that are supported by the relevant applications of the networked system 1502.
- FIG. 16 is a block diagram illustrating multiple applications 1520 and 1522 that, in one example embodiment, are provided as part of the networked system 1502.
- the applications 1520 and 1522 may be hosted on dedicated or shared server machines (not shown) that are communicatively coupled to enable communications between server machines.
- the applications 1520 and 1522 themselves are communicatively coupled (e.g., via appropriate interfaces) to each other and to various data sources, so as to allow information to be passed between the applications 1520 and 1522, or so as to allow the applications 1520 and 1522 to share and access common data.
- the applications 1520 and 1522 may furthermore access one or more databases 1526 via the database servers 1524 of FIG. 15.
- the networked system 1502 may provide a number of publishing, listing and price-setting mechanisms whereby a seller may list (or publish information concerning) goods or services for sale, a buyer can express interest in or indicate a desire to purchase such goods or services, and a price can be set for a transaction pertaining to the goods or services.
- the marketplace and payment applications 1520 and 1522 are shown to include at least one publication application 1600 and one or more auction applications 1602 which support auction-format listing and price setting mechanisms (e.g., English, Dutch, Vickrey, Chinese, Double, Reverse auctions etc.).
- the various auction applications 1602 may also provide a number of features in support of such auction-format listings, such as a reserve price feature whereby a seller may specify a reserve price in connection with a listing, and a proxy-bidding feature whereby a bidder may invoke automated proxy bidding.
- a reserve price feature whereby a seller may specify a reserve price in connection with a listing
- a proxy-bidding feature whereby a bidder may invoke automated proxy bidding.
- a number of fixed-price applications 1604 support fixed-price listing formats (e.g., the traditional classified advertisement-type listing or a catalogue listing) and buyout-type listings.
- buyout-type listings e.g., including the Buy-It-Now (BIN) technology developed by eBay Inc., of San Jose, California
- BIN Buy-It-Now
- auction-format listings may be offered in conjunction with auction-format listings, and allow a buyer to purchase goods or services, which are also being offered for sale via an auction, for a fixed-price that is typically higher than the starting price of the auction.
- Store applications 1606 allow a seller to group listings within a "virtual" store, which may be branded and otherwise personalized by and for the seller. Such a virtual store may also offer promotions, incentives and features that are specific and personalized to a relevant seller.
- Reputation applications 1608 allow users that transact, utilizing the networked system 1502, to establish, build and maintain reputations, which may be made available and published to potential trading partners.
- the reputation applications 1608 allow a user (for example through feedback provided by other transaction partners) to establish a reputation within the networked system 1502 over time. Other potential trading partners may then reference such a reputation for the purposes of assessing credibility and trustworthiness.
- Personalization applications 1610 allow users of the networked system 1502 to personalize various aspects of their interactions with the networked system 1502. For example a user may, utilizing an appropriate personalization application 1610, create a personalized reference page at which information regarding transactions to which the user is (or has been) a party may be viewed. Further, a personalization application 1610 may enable a user to personalize listings and other aspects of their interactions with the networked system 1502 and other parties.
- the networked system 1502 may support a number of marketplaces that are customized, for example, for specific geographic regions.
- a version of the networked system 1 02 may be customized for the United Kingdom, whereas another version of the networked system 1502 may be customized for the United States.
- Each of these versions may operate as an independent marketplace, or may be customized (or internationalized) presentations of a common underlying marketplace.
- the networked system 1502 may accordingly include a number of internationalization applications 1612 that customize information (and/or the presentation of information) by the networked system 1502 according to predetermined criteria (e.g., geographic, demographic or marketplace criteria).
- predetermined criteria e.g., geographic, demographic or marketplace criteria
- the internationalization applications 1612 may be used to support the customization of information for a number of regional websites that are operated by the networked system 1502 and that are accessible via respective web servers 1516 (FIG. 15).
- Navigation of the networked system 1502 may be facilitated by one or more navigation applications 1614.
- the marketplace and payment applications 1520 and 1522 may include one or more imaging applications 1616 which users may utilize to upload images for inclusion within listings.
- An imaging application 1616 also operates to incorporate images within viewed listings.
- the imaging applications 1616 may also support one or more promotional features, such as image galleries that are presented to potential buyers. For example, sellers may pay an additional fee to have an image included within a gallery of images for promoted items.
- Listing creation applications 1618 allow sellers to conveniently author listings pertaining to goods or services that they wish to transact via the networked system 1502, and listing management applications 1620 allow sellers to manage such listings. Specifically, where a particular seller has authored and/or published a large number of listings, the management of such listings may present a challenge.
- the listing management applications 1620 provide a number of features (e.g., auto-relisting, inventory level monitors, etc.) to assist the seller in managing such listings.
- One or more post-listing management applications 1622 also assist sellers with a number of activities that typically occur post-listing. For example, upon completion of an auction facilitated by one or more auction applications 1602, a seller may wish to leave feedback regarding a particular buyer. To this end, a post-listing management application 1622 may provide an interface to one or more reputation applications 1608, so as to allow the seller to conveniently provide feedback regarding multiple buyers to the reputation applications 1608.
- Dispute resolution applications 1624 provide mechanisms whereby disputes arising between transacting parties may be resolved.
- the dispute resolution applications 1624 may provide guided procedures whereby the parties are guided through a number of operations in an attempt to settle a dispute. In the event that the dispute cannot be settled via the guided procedures, the dispute may be escalated to a third party mediator or arbitrator.
- a number of fraud prevention applications 1626 implement fraud detection and prevention mechanisms to reduce the occurrence of fraud within the networked system 1502.
- Messaging applications 1628 are responsible for the generation and delivery of messages to users of the networked system 1502. These messages may, for example, advise users regarding the status of listings at the networked system 1502 (e.g., providing "outbid” notices to bidders during an auction process or providing promotional and merchandising information to users). Respective messaging applications 1628 may utilize any one of a number of message delivery networks and platforms to deliver messages to users.
- messaging applications 1628 may deliver electronic mail (e-mail), instant message (IM), Short Message Service (SMS), text, facsimile, or voice (e.g., Voice over IP (VoIP)) messages via the wired (e.g., the Internet), Plain Old Telephone Service (POTS), or wireless (e.g., mobile, cellular, WiFi, WiMAX) networks.
- e-mail electronic mail
- IM instant message
- SMS Short Message Service
- text e.g., text
- facsimile e.g., facsimile
- voice e.g., Voice over IP (VoIP)
- POTS Plain Old Telephone Service
- wireless e.g., mobile, cellular, WiFi, WiMAX
- Merchandising applications 1630 support various merchandising functions that are made available to sellers to enable sellers to increase sales via the networked system 1502.
- the merchandising applications 1630 also operate the various merchandising features that may be invoked by sellers, and may monitor and track the success of merchandising strategies employed by sellers.
- the networked system 1502 itself, or one or more parties that transact via the networked system 1502, may operate loyally programs that are supported by one or more loyalty/promotion applications 1632. For example, a buyer may earn loyalty or promotions points for each transaction established and/or concluded with a particular seller, and may be offered a reward for which accumulated loyalty points can be redeemed.
- Modules may constitute either software modules (e.g., code embodied on a machine-readable medium or in a transmission signal) or hardware modules.
- a hardware module is a tangible unit capable of performing certain operations and may be configured or arranged in a certain manner.
- one or more computer systems e.g., a standalone, client or server computer system
- one or more hardware modules of a computer system e.g., a processor or a group of processors
- software e.g., an application or application portion
- a hardware module may be implemented mechanically or electronically.
- a hardware module may comprise dedicated circuitry or logic that is permanently configured (e.g., as a special- purpose processor, such as a field programmable gate array (FPGA) or an application-specific integrated circuit (ASIC)) to perform certain operations.
- a hardware module may also comprise programmable logic or circuitry (e.g., as encompassed within a general-purpose processor or other programmable processor) that is temporarily configured by software to perform certain operations. It will be appreciated that the decision to implement a hardware module mechanically, in dedicated and permanently configured circuitry, or in temporarily configured circuitry (e.g., configured by software) may be driven by cost and time considerations.
- the term "hardware module” should be understood to encompass a tangible entity, be that an entity that is physically constructed, permanently configured (e.g., hardwired) or temporarily configured (e.g., programmed) to operate in a certain manner and/or to perform certain operations described herein.
- hardware modules are temporarily configured (e.g., programmed)
- each of the hardware modules need not be configured or instantiated at any one instance in time.
- the hardware modules comprise a general-purpose processor configured using software
- the general-purpose processor may be configured as respective different hardware modules at different times.
- Software may accordingly configure a processor, for example, to constitute a particular hardware module at one instance of time and to constitute a different hardware module at a different instance of time.
- Hardware modules can provide information to, and receive information from, other hardware modules. Accordingly, the described hardware modules may be regarded as being communicatively coupled. Where multiple such hardware modules exist contemporaneously, communications may be achieved through signal transmission (e.g., over appropriate circuits and buses) that connect the hardware modules. In embodiments in which multiple hardware modules are configured or instantiated at different times, communications between such hardware modules may be achieved, for example, through the storage and retrieval of information in memory structures to which the multiple hardware modules have access. For example, one hardware module may perform an operation and store the output of that operation in a memory device to which it is communicatively coupled. A further hardware module may then, at a later time, access the memory device to retrieve and process the stored output. Hardware modules may also initiate communications with input or output devices and can operate on a resource (e.g., a collection of information).
- a resource e.g., a collection of information
- processors may be temporarily configured (e.g., by software) or permanently configured to perform the relevant operations. Whether temporarily or permanently configured, such processors may constitute processor-implemented modules that operate to perform one or more operations or functions.
- the modules referred to herein may, in some example embodiments, comprise processor-implemented modules.
- the methods described herein may be at least partially processor-implemented. For example, at least some of the operations of a method may be performed by one or processors or processor-implemented modules. The performance of certain of the operations may be distributed among the one or more processors, not only residing within a single machine, but deployed across a number of machines. In some example embodiments, the processor or processors may be located in a single location (e.g., within a home environment, an office environment or as a server farm), while in other embodiments the processors may be distributed across a number of locations.
- the one or more processors may also operate to support performance of the relevant operations in a "cloud computing" environment or as a “software as a service” (SaaS). For example, at least some of the operations may be performed by a group of computers (as examples of machines including processors), these operations being accessible via a network (e.g., the Internet) and via one or more appropriate interfaces (e.g., APIs).
- SaaS software as a service
- Example embodiments may be implemented in digital electronic circuitry, or in computer hardware, firmware, software, or in combinations of them.
- Example embodiments may be implemented using a computer program product, e.g., a computer program tangibly embodied in an information carrier, e.g., in a machine-readable medium for execution by, or to control the operation of, data processing apparatus, e.g., a programmable processor, a computer, or multiple computers.
- a computer program can be written in any form of programming language, including compiled or interpreted languages, and it can be deployed in any form, including as a stand-alone program or as a module, subroutine, or other unit suitable for use in a computing environment.
- a computer program can be deployed to be executed on one computer or on multiple computers at one site or distributed across multiple sites and interconnected by a communication network.
- operations may be performed by one or more programmable processors executing a computer program to perform functions by operating on input data and generating output. Method operations can also be performed by, and apparatus of example embodiments may be implemented as, special purpose logic circuitry, e.g., a field programmable gate array (FPGA) or an application-specific integrated circuit (ASIC).
- FPGA field programmable gate array
- ASIC application-specific integrated circuit
- the computing system can include clients and servers.
- a client and server are generally remote from each other and typically interact through a communication network.
- the relationship of client and server arises by virtue of computer programs running on the respective computers and having a client- server relationship to each other.
- both hardware and software architectures require consideration.
- the choice of whether to implement certain functionality in permanently configured hardware e.g., an ASIC
- temporarily configured hardware e.g., a combination of software and a programmable processor
- a combination of permanently and temporarily configured hardware may be a design choice.
- hardware e.g., machine
- software architectures that may be deployed, in various example embodiments.
- FIG 17 is a block diagram of machine in the example form of a computer system 1700 within which instructions for causing the machine to perform any one or more of the methodologies discussed herein may be executed.
- the machine operates as a standalone device or may be connected (e.g., networked) to other machines.
- the machine may operate in the capacity of a server or a client machine in server-client network environment, or as a peer machine in a peer-to- peer (or distributed) network environment.
- the machine may be a personal computer (PC), a tablet PC, a set-top box (STB), a Personal Digital Assistant (PDA), a cellular telephone, a web appliance, a network router, switch or bridge, or any machine capable of executing instructions (sequential or otherwise) that specify actions to be taken by that machine.
- PC personal computer
- PDA Personal Digital Assistant
- STB set-top box
- WPA Personal Digital Assistant
- a cellular telephone a web appliance
- network router switch or bridge
- machine any machine capable of executing instructions (sequential or otherwise) that specify actions to be taken by that machine.
- machine shall also be taken to include any collection of machines that individually or jointly execute a set (or multiple sets) of instructions to perform any one or more of the methodologies discussed herein.
- the example computer system 1700 includes a processor 1702 (e.g., a central processing unit (CPU), a graphics processing unit (GPU) or both), a main memory 1704 and a static memory 1706, which communicate with each other via a bus 1708.
- the computer system 1700 may further include a video display unit 1710 (e.g., a liquid crystal display (LCD) or a cathode ray tube (CRT)).
- LCD liquid crystal display
- CRT cathode ray tube
- the computer system 1700 also includes an alphanumeric input device 1712 (e.g., a keyboard), a user interface (UI) navigation (or cursor control) device 1714 (e.g., a mouse), a disk drive unit 1716, a signal generation device 1718 (e.g., a speaker) and a network interface device 1720.
- UI user interface
- cursor control or cursor control
- the disk drive unit 1716 includes a machine-readable medium 1722 on which is stored one or more sets of instructions 1724 and data structures (e.g., software) embodying or utilized by any one or more of the methodologies or functions described herein.
- the instructions 1724 may also reside, completely or at least partially, within the main memory 1704 and/or within the processor 1702 during execution thereof by the computer system 1700, the main memory 1704 and the processor 1702 also constituting machine-readable media.
- the instructions 1724 may also reside, completely or at least partially, within the static memory 1706.
- machine-readable medium 1722 is shown in an example embodiment to be a single medium, the term “machine-readable medium” may include a single medium or multiple media (e.g., a centralized or distributed database, and/or associated caches and servers) that store the one or more instructions 1724 or data structures.
- the term “machine-readable medium” shall also be taken to include any tangible medium that is capable of storing, encoding or carrying instructions for execution by the machine and that cause the machine to perform any one or more of the methodologies of the present embodiments, or that is capable of storing, encoding or carrying data structures utilized by or associated with such instructions.
- the term “machine-readable medium” shall accordingly be taken to include, but not be limited to, solid-state memories, and optical and magnetic media.
- machine-readable media include non- volatile memory, including by way of example semiconductor memory devices, e.g., Erasable Programmable Read-Only Memory (EPROM), Electrically Erasable Programmable Read-Only Memory (EEPROM), and flash memory devices; magnetic disks such as internal hard disks and removable disks; magneto-optical disks; and compact disc-read-only memory (CD-ROM) and digital versatile disc (or digital video disc) read-only memory (DVD-ROM) disks.
- semiconductor memory devices e.g., Erasable Programmable Read-Only Memory (EPROM), Electrically Erasable Programmable Read-Only Memory (EEPROM), and flash memory devices
- EPROM Erasable Programmable Read-Only Memory
- EEPROM Electrically Erasable Programmable Read-Only Memory
- flash memory devices e.g., electrically Erasable Programmable Read-Only Memory (EEPROM), and flash memory devices
- magnetic disks such as internal hard disks and removable disks
- the instructions 1724 may further be transmitted or received over a communications network 1726 using a transmission medium.
- the instructions 1724 may be transmitted using the network interface device 1720 and any one of a number of well-known transfer protocols (e.g., Hyper Text Transfer Protocol or HTTP).
- Examples of communication networks include a local area network ("LAN”), a wide area network (“WAN”), the Internet, mobile telephone networks, Plain Old Telephone (POTS) networks, and wireless data networks (e.g., WiFi and WiMax networks).
- POTS Plain Old Telephone
- the term "transmission medium” shall be taken to include any intangible medium that is capable of storing, encoding or carrying instructions for execution by the machine, and includes digital or analog communications signals or other intangible media to facilitate communication of such software.
- inventive subject matter may be referred to herein, individually and/or collectively, by the term "invention" merely for convenience and without intending to voluntarily limit the scope of this application to any single invention or inventive concept if more than one is in fact disclosed.
- inventive subject matter may be referred to herein, individually and/or collectively, by the term "invention" merely for convenience and without intending to voluntarily limit the scope of this application to any single invention or inventive concept if more than one is in fact disclosed.
- inventive subject matter merely for convenience and without intending to voluntarily limit the scope of this application to any single invention or inventive concept if more than one is in fact disclosed.
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Software Systems (AREA)
- General Engineering & Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Multimedia (AREA)
- Stored Programmes (AREA)
- Human Computer Interaction (AREA)
- Telephonic Communication Services (AREA)
Abstract
Description
Claims
Priority Applications (7)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
KR1020127023102A KR101628433B1 (en) | 2010-02-05 | 2011-01-21 | An apparatus, a method and a machine-readable storage medium for optimizing calls to a service by components of an application running on the application server |
KR1020147027561A KR101660148B1 (en) | 2010-02-05 | 2011-01-21 | An apparatus, a method and a machine-readable storage medium for optimizing calls to a service by components of an application running on the application server |
CA2788899A CA2788899C (en) | 2010-02-05 | 2011-01-21 | Widget framework, real-time service orchestration, and real-time resource aggregation |
KR1020157009935A KR101703196B1 (en) | 2010-02-05 | 2011-01-21 | An apparatus, a method and a machine-readable storage medium for optimizing calls to a service by components of an application running on the application server |
EP11740184.4A EP2531926A4 (en) | 2010-02-05 | 2011-01-21 | Widget framework, real-time service orchestration, and real-time resource aggregation |
AU2011213189A AU2011213189B2 (en) | 2010-02-05 | 2011-01-21 | Widget framework, real-time service orchestration, and real-time resource aggregation |
JP2012551993A JP5582428B2 (en) | 2010-02-05 | 2011-01-21 | Widget framework, real-time service integration and real-time resource aggregation |
Applications Claiming Priority (4)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US30208210P | 2010-02-05 | 2010-02-05 | |
US61/302,082 | 2010-02-05 | ||
US12/754,564 US9367371B2 (en) | 2010-02-05 | 2010-04-05 | Widget framework, real-time service orchestration, and real-time resource aggregation |
US12/754,564 | 2010-04-05 |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2011097078A1 true WO2011097078A1 (en) | 2011-08-11 |
Family
ID=44354666
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/US2011/022109 WO2011097078A1 (en) | 2010-02-05 | 2011-01-21 | Widget framework, real-time service orchestration, and real-time resource aggregation |
Country Status (7)
Country | Link |
---|---|
US (2) | US9367371B2 (en) |
EP (1) | EP2531926A4 (en) |
JP (3) | JP5582428B2 (en) |
KR (3) | KR101628433B1 (en) |
AU (1) | AU2011213189B2 (en) |
CA (1) | CA2788899C (en) |
WO (1) | WO2011097078A1 (en) |
Cited By (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US9367371B2 (en) | 2010-02-05 | 2016-06-14 | Paypal, Inc. | Widget framework, real-time service orchestration, and real-time resource aggregation |
Families Citing this family (18)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US9781049B2 (en) * | 2010-05-07 | 2017-10-03 | Salesforce.Com, Inc. | Resolving information in a database environment |
US9069905B2 (en) | 2012-07-16 | 2015-06-30 | Microsoft Technology Licensing, Llc | Tool-based testing for composited systems |
US9621635B1 (en) * | 2012-07-31 | 2017-04-11 | Niantic, Inc. | Using side channels in remote procedure calls to return information in an interactive environment |
US9189619B2 (en) | 2012-11-13 | 2015-11-17 | International Business Machines Corporation | Runtime based application security and regulatory compliance in cloud environment |
US9195294B2 (en) | 2012-11-13 | 2015-11-24 | International Business Machines Corporation | Cooperatively managing enforcement of energy related policies between virtual machine and application runtime |
CN104252412B (en) * | 2013-06-28 | 2017-12-29 | 国际商业机器公司 | Method and system for the automatic detection of CSS conflicts |
US9760345B2 (en) * | 2014-07-26 | 2017-09-12 | Alfonso Diez | Recursive ontology-based systems engineering |
US9398081B2 (en) * | 2014-08-20 | 2016-07-19 | Futurewei Technologies, Inc. | Automating client development for network APIs |
US10579354B2 (en) * | 2015-03-10 | 2020-03-03 | Kordata, Llc | Method and system for rapid deployment and execution of customized functionality across multiple distinct platforms |
US9900380B2 (en) | 2015-07-14 | 2018-02-20 | Bank Of America Corporation | Common function modules for use with multiple applications |
US10802660B1 (en) * | 2015-07-29 | 2020-10-13 | Intuit Inc. | Metadata-driven binding of platform-agnostic content to platform-specific user-interface elements |
US9672140B1 (en) * | 2015-12-28 | 2017-06-06 | Sap Se | Processing special requests at dedicated application containers |
US11010024B2 (en) | 2018-03-29 | 2021-05-18 | Cerner Innovation, Inc. | Intelligent user interface and application rendering |
US11379497B2 (en) * | 2018-06-21 | 2022-07-05 | At&T Intellectual Property I, L.P. | Data model database |
WO2021101546A1 (en) * | 2019-11-21 | 2021-05-27 | Schlumberger Technology Corporation | Widget delivery workflow system and method |
US10977059B1 (en) * | 2020-03-25 | 2021-04-13 | Red Hat, Inc. | Implementing object validation, web request handling, object relational mapping, or messaging via direct bytecode generation |
CN114237413A (en) * | 2020-09-09 | 2022-03-25 | 华为技术有限公司 | Method and device for processing interaction event |
US11816456B2 (en) * | 2020-11-16 | 2023-11-14 | Microsoft Technology Licensing, Llc | Notebook for navigating code using machine learning and flow analysis |
Citations (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20050080930A1 (en) | 2003-10-14 | 2005-04-14 | International Business Machines Corporation | Method and apparatus for processing service requests in a service-oriented architecture |
US7110525B1 (en) * | 2001-06-25 | 2006-09-19 | Toby Heller | Agent training sensitive call routing system |
US20070291776A1 (en) * | 2005-07-28 | 2007-12-20 | Dilithium Networks, Inc. | Method and apparatus for billing for media during communications in channel-based media telecommunication protocols |
US20080313659A1 (en) * | 2007-06-15 | 2008-12-18 | Microsoft Corporation | Page and device-optimized cascading style sheets |
US20090073938A1 (en) * | 2006-04-27 | 2009-03-19 | Huawei Technologies Co., Ltd. | Method, system and apparatus for optimizing call anchoring in voice call continuity |
Family Cites Families (36)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5325524A (en) * | 1989-04-06 | 1994-06-28 | Digital Equipment Corporation | Locating mobile objects in a distributed computer system |
US5649103A (en) | 1995-07-13 | 1997-07-15 | Cabletron Systems, Inc. | Method and apparatus for managing multiple server requests and collating reponses |
US6321274B1 (en) * | 1996-06-28 | 2001-11-20 | Microsoft Corporation | Multiple procedure calls in a single request |
US6427234B1 (en) * | 1998-06-11 | 2002-07-30 | University Of Washington | System and method for performing selective dynamic compilation using run-time information |
JP2000099332A (en) * | 1998-09-25 | 2000-04-07 | Hitachi Ltd | Remote procedure call optimization method and program execution method using the optimization method |
US7281268B2 (en) | 1999-11-14 | 2007-10-09 | Mcafee, Inc. | System, method and computer program product for detection of unwanted processes |
US20020078103A1 (en) | 2000-12-20 | 2002-06-20 | Gorman William Phillip | Wizard development kit |
US8069225B2 (en) | 2003-04-14 | 2011-11-29 | Riverbed Technology, Inc. | Transparent client-server transaction accelerator |
CN1799026A (en) * | 2003-06-05 | 2006-07-05 | 瑞士再保险公司 | Method and terminal for generating uniform device-independent graphical user interfaces |
WO2005009412A1 (en) * | 2003-07-24 | 2005-02-03 | Wockhardt Limited | Oral compositions for treatment of diseases |
US7421700B2 (en) * | 2004-03-15 | 2008-09-02 | Microsoft Corporation | Interprocess buffer management using a buffer delay time |
JP4163670B2 (en) | 2004-05-10 | 2008-10-08 | 株式会社ソニー・コンピュータエンタテインメント | Disk unit |
WO2006026636A2 (en) | 2004-08-31 | 2006-03-09 | Ascential Software Corporation | Metadata management |
JP4280703B2 (en) | 2004-11-09 | 2009-06-17 | 日立オムロンターミナルソリューションズ株式会社 | Interprocess communication |
US7706895B2 (en) * | 2005-02-25 | 2010-04-27 | Rockwell Automation Technologies, Inc. | Reliable messaging instruction |
US7457797B2 (en) * | 2005-03-30 | 2008-11-25 | International Business Machines Corporation | Method and apparatus for associating logical conditions with the re-use of a database query execution strategy |
US7912810B2 (en) * | 2005-06-28 | 2011-03-22 | Sap Ag | Methods, systems and computer program products for integrating carrier services into an enterprise |
US7890955B2 (en) * | 2006-04-03 | 2011-02-15 | Microsoft Corporation | Policy based message aggregation framework |
US20070240041A1 (en) * | 2006-04-05 | 2007-10-11 | Larry Pearson | Methods and apparatus for generating an aggregated cascading style sheet |
US9074364B2 (en) * | 2006-06-17 | 2015-07-07 | Rotating High Towers S.A. | Rotatable building structure |
US20080228920A1 (en) * | 2007-03-16 | 2008-09-18 | Souders Steven K | System and method for resource aggregation and distribution |
US8341595B2 (en) * | 2007-05-30 | 2012-12-25 | Roam Data Inc | System and method for developing rich internet applications for remote computing devices |
US8156164B2 (en) * | 2007-07-11 | 2012-04-10 | International Business Machines Corporation | Concurrent directory update in a cluster file system |
DE602007007941D1 (en) * | 2007-08-13 | 2010-09-02 | Accenture Global Services Gmbh | Service Request Execution Architecture for a Communication Service Provider |
US8285813B1 (en) * | 2007-12-05 | 2012-10-09 | Appcelerator, Inc. | System and method for emulating different user agents on a server |
US8176205B2 (en) | 2008-02-14 | 2012-05-08 | Research In Motion Limited | Method, server and system for optimizing HTML-based content |
JP2009205264A (en) | 2008-02-26 | 2009-09-10 | Nippon Telegr & Teleph Corp <Ntt> | Web service request processing apparatus, web service request processing method, and web service request processing system |
NZ566291A (en) * | 2008-02-27 | 2008-12-24 | Actionthis Ltd | Methods and devices for post processing rendered web pages and handling requests of post processed web pages |
US9110685B2 (en) | 2008-03-25 | 2015-08-18 | Qualcomm, Incorporated | Apparatus and methods for managing widgets in a wireless communication environment |
US8010624B2 (en) | 2008-03-27 | 2011-08-30 | Amazon Technologies, Inc. | Dynamic composition for image transmission |
US8234622B2 (en) | 2008-03-31 | 2012-07-31 | Microsoft Corporation | Cross platform compositional widgets |
CN101572598B (en) | 2008-04-28 | 2013-03-06 | 国际商业机器公司 | Method and device for reliable rapid integration |
JP2009290729A (en) | 2008-05-30 | 2009-12-10 | Ricoh Co Ltd | Image forming apparatus, information processing method, and program |
US8990289B2 (en) * | 2009-02-27 | 2015-03-24 | Oracle America, Inc. | Server based framework for improving Ajax performance |
US8572554B2 (en) * | 2009-07-17 | 2013-10-29 | Ebay Inc. | Method and system for integrating Java and JavaScript technologies |
US9367371B2 (en) | 2010-02-05 | 2016-06-14 | Paypal, Inc. | Widget framework, real-time service orchestration, and real-time resource aggregation |
-
2010
- 2010-04-05 US US12/754,564 patent/US9367371B2/en active Active
-
2011
- 2011-01-21 JP JP2012551993A patent/JP5582428B2/en active Active
- 2011-01-21 AU AU2011213189A patent/AU2011213189B2/en active Active
- 2011-01-21 EP EP11740184.4A patent/EP2531926A4/en not_active Withdrawn
- 2011-01-21 WO PCT/US2011/022109 patent/WO2011097078A1/en active Application Filing
- 2011-01-21 KR KR1020127023102A patent/KR101628433B1/en active IP Right Grant
- 2011-01-21 KR KR1020147027561A patent/KR101660148B1/en active IP Right Grant
- 2011-01-21 KR KR1020157009935A patent/KR101703196B1/en active IP Right Grant
- 2011-01-21 CA CA2788899A patent/CA2788899C/en active Active
-
2014
- 2014-07-03 JP JP2014137315A patent/JP5809328B2/en active Active
-
2015
- 2015-09-10 JP JP2015178085A patent/JP2016026348A/en active Pending
-
2016
- 2016-05-18 US US15/157,882 patent/US20160266949A1/en not_active Abandoned
Patent Citations (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US7110525B1 (en) * | 2001-06-25 | 2006-09-19 | Toby Heller | Agent training sensitive call routing system |
US20050080930A1 (en) | 2003-10-14 | 2005-04-14 | International Business Machines Corporation | Method and apparatus for processing service requests in a service-oriented architecture |
US20070291776A1 (en) * | 2005-07-28 | 2007-12-20 | Dilithium Networks, Inc. | Method and apparatus for billing for media during communications in channel-based media telecommunication protocols |
US20090073938A1 (en) * | 2006-04-27 | 2009-03-19 | Huawei Technologies Co., Ltd. | Method, system and apparatus for optimizing call anchoring in voice call continuity |
US20080313659A1 (en) * | 2007-06-15 | 2008-12-18 | Microsoft Corporation | Page and device-optimized cascading style sheets |
Non-Patent Citations (1)
Title |
---|
See also references of EP2531926A4 |
Cited By (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US9367371B2 (en) | 2010-02-05 | 2016-06-14 | Paypal, Inc. | Widget framework, real-time service orchestration, and real-time resource aggregation |
Also Published As
Publication number | Publication date |
---|---|
KR20120128661A (en) | 2012-11-27 |
JP2014211898A (en) | 2014-11-13 |
KR101660148B1 (en) | 2016-09-26 |
JP5809328B2 (en) | 2015-11-10 |
AU2011213189B2 (en) | 2014-11-06 |
US20160266949A1 (en) | 2016-09-15 |
JP2013519158A (en) | 2013-05-23 |
KR20140130532A (en) | 2014-11-10 |
US20110197197A1 (en) | 2011-08-11 |
CA2788899C (en) | 2016-12-13 |
KR101703196B1 (en) | 2017-02-06 |
CA2788899A1 (en) | 2011-08-11 |
JP2016026348A (en) | 2016-02-12 |
AU2011213189A1 (en) | 2012-08-30 |
JP5582428B2 (en) | 2014-09-03 |
KR101628433B1 (en) | 2016-06-08 |
US9367371B2 (en) | 2016-06-14 |
EP2531926A1 (en) | 2012-12-12 |
KR20150048903A (en) | 2015-05-07 |
EP2531926A4 (en) | 2015-08-26 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
AU2011213189B2 (en) | Widget framework, real-time service orchestration, and real-time resource aggregation | |
US10216554B2 (en) | API notebook tool | |
US8898285B2 (en) | Service oriented architecture version and dependency control | |
Jendrock et al. | Java EE 7 Tutorial, The, Volume 1 | |
US8584082B2 (en) | System for dynamic discovery, configuration, and development of process-bound widgets | |
US9015532B2 (en) | System and method to test executable instructions | |
US9898263B2 (en) | System and method for resource-definition-oriented software generation and development | |
US20110023013A1 (en) | System and Method For Generating Component Based Applications | |
US11797273B2 (en) | System and method for enhancing component based development models with auto-wiring | |
US20200293339A1 (en) | Network address management systems and methods | |
EP2779582B1 (en) | Automatic mobile application discovery and integration in a mobile telecommunication device | |
JP2010504591A (en) | Common component framework | |
AU2016203934B2 (en) | Widget framework, real-time service orchestration, and real-time resource aggregation | |
US11443011B2 (en) | Page objects library | |
Paz | Beginning ASP. NET MVC 4 | |
AU2015200369B2 (en) | Widget framework, real-time service orchestration, and real-time resource aggregation | |
US20240069933A1 (en) | Database systems and client-side field retrieval methods | |
Wenzel | Action links | |
Soltani | Enabling run-time state migration between same-purpose applications of different vendors | |
Karus | XML development with plug‐ins as a service | |
Troelsen et al. | Introducing ASP. NET Web Forms | |
Moraza Erauskin | Reuse of software components orientated to iOS mobile devices | |
Kettner et al. | Pro Serverless Data Handling with Microsoft Azure |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 11740184 Country of ref document: EP Kind code of ref document: A1 |
|
DPE1 | Request for preliminary examination filed after expiration of 19th month from priority date (pct application filed from 20040101) | ||
WWE | Wipo information: entry into national phase |
Ref document number: 2012551993 Country of ref document: JP |
|
ENP | Entry into the national phase |
Ref document number: 2788899 Country of ref document: CA |
|
NENP | Non-entry into the national phase |
Ref country code: DE |
|
WWE | Wipo information: entry into national phase |
Ref document number: 2011213189 Country of ref document: AU |
|
WWE | Wipo information: entry into national phase |
Ref document number: 2011740184 Country of ref document: EP |
|
ENP | Entry into the national phase |
Ref document number: 2011213189 Country of ref document: AU Date of ref document: 20110121 Kind code of ref document: A |
|
ENP | Entry into the national phase |
Ref document number: 20127023102 Country of ref document: KR Kind code of ref document: A |