U.S. patent application number 17/126766 was filed with the patent office on 2021-07-08 for multi-channel session connection management mechanism.
The applicant listed for this patent is salesforce.com, inc.. Invention is credited to SOUMEN BANDYOPADHYAY, JOHN ARLAN BROCK, JAY HURST, VIKRAM KOMMARAJU, PURUSHOTHAM BABU NAIDU.
Application Number | 20210211507 17/126766 |
Document ID | / |
Family ID | 1000005478178 |
Filed Date | 2021-07-08 |
United States Patent
Application |
20210211507 |
Kind Code |
A1 |
NAIDU; PURUSHOTHAM BABU ; et
al. |
July 8, 2021 |
MULTI-CHANNEL SESSION CONNECTION MANAGEMENT MECHANISM
Abstract
Techniques and structures to manage a multi-channel
client-server connection is disclosed. A connection session is
established between a client and in server response to receiving a
call from a first browser interface element to establish the
connection session. The session is shared in response to receiving
a second call from a second browser interface element to establish
a connection session.
Inventors: |
NAIDU; PURUSHOTHAM BABU;
(Lafayette, CO) ; HURST; JAY; (San Francisco,
CA) ; BROCK; JOHN ARLAN; (Oakland, CA) ;
KOMMARAJU; VIKRAM; (San Francisco, CA) ;
BANDYOPADHYAY; SOUMEN; (Castro Valley, CA) |
|
Applicant: |
Name |
City |
State |
Country |
Type |
salesforce.com, inc. |
San Francisco |
CA |
US |
|
|
Family ID: |
1000005478178 |
Appl. No.: |
17/126766 |
Filed: |
December 18, 2020 |
Related U.S. Patent Documents
|
|
|
|
|
|
Application
Number |
Filing Date |
Patent Number |
|
|
16139988 |
Sep 24, 2018 |
10873635 |
|
|
17126766 |
|
|
|
|
Current U.S.
Class: |
1/1 |
Current CPC
Class: |
H04L 67/42 20130101;
H04L 67/141 20130101; H04L 65/1093 20130101 |
International
Class: |
H04L 29/08 20060101
H04L029/08; H04L 29/06 20060101 H04L029/06 |
Claims
1-20. (canceled)
21. A method for managing a multi-channel client-server connection,
comprising: receiving, at a client computing device, a call to
establish a first subscription channel with a server computing
device, wherein the first subscription channel comprises a channel
between a first application page operating in a first browser
interface element; establishing a session connection between the
client computing device and the server computing device, comprising
establishing the first subscription channel between the first
application page and the server computing device; receiving, at the
client computing device, a second call to establish a second
subscription channel with the server computing device, wherein the
second subscription channel comprises a channel between a second
application page operating in a second browser interface element;
establishing the second subscription channel between the second
application page and the server computing device; and managing a
sharing of data transfers with the server computing device over the
first subscription channel and data transfers with the server
computing device over the second subscription channel via the
session connection, wherein the first subscription channel is
different from the second subscription channel.
22. The method of claim 21, further comprising: transferring first
data between the client computing device and the server computing
device over the first subscription channel via the session
connection; and transferring second data between the client
computing device and the server computing device over the second
subscription channel via the session connection.
23. The method of claim 21, wherein managing the sharing of the
session connection comprises multiplexing data transfers between
the first subscription channel and the second subscription channel
via the session connection.
24. The method of claim 21, wherein managing the sharing of the
session connection comprises the first subscription channel and the
second subscription channel accessing the session connection via a
shared browser interface component.
25. The method of claim 21, wherein managing the sharing of the
session connection comprises the first subscription channel and the
second subscription channel accessing the session connection via
dedicated worker browser interface components.
26. The method of claim 21, wherein the call to establish the first
subscription channel is received from a first browser interface
element and the second call to establish the second subscription
channel is received from a second browser interface element.
27. The method of claim 26, wherein the first browser interface
element comprises a first browser tab and the second browser
interface element comprises a second browser tab.
28. A non-transitory computer-readable medium having stored thereon
instructions that, when executed by one or more processors, are
configurable to cause the one or more processors to: receive, at a
client computing device, a call to establish a first subscription
channel with a server computing device, wherein the first
subscription channel comprises a channel between a first
application page operating in a first browser interface element;
establish a session connection between the client computing device
and the server computing device, comprising establishing the first
subscription channel between the first application page and the
server computing device; receive, at the client computing device, a
second call to establish a second subscription channel with the
server computing device, wherein the second subscription channel
comprises a channel between a second application page operating in
a second browser interface element; establish the second
subscription channel between the second application page and the
server computing device; and manage a sharing of-data transfers
with the server computing device over the first subscription
channel and data transfers with the server computing device over
the second subscription channel via the session connection, wherein
the first subscription channel is different from the second
subscription channel.
29. The non-transitory computer-readable medium of claim 8, having
stored thereon instructions that, when executed by one or more
processors, are configurable to further cause the one or more
processors to: transfer first data between the client computing
device and the server computing device over the first subscription
channel via the session connection; and transfer second data
between the client computing device and the server computing device
over the second subscription channel via the session
connection.
30. The non-transitory computer-readable medium of claim 8, wherein
managing the sharing of the session connection comprises
multiplexing data transfers between the first subscription channel
and the second subscription channel via the session connection.
31. The non-transitory computer-readable medium of claim 28,
wherein managing the sharing of the session connection comprises
the first subscription channel and the second subscription channel
accessing the session connection via a shared browser interface
component.
32. The non-transitory computer-readable medium of claim 28,
wherein managing the sharing of the session connection comprises
the first subscription channel and the second subscription channel
accessing the session connection via dedicated worker browser
interface components.
33. The non-transitory computer-readable medium of claim 28,
wherein the call to establish the first subscription channel is
received from a first browser interface element and the second call
to establish the second subscription channel is received from a
second browser interface element.
34. The non-transitory computer-readable medium of claim 33,
wherein the first browser interface element comprises a first
browser window and the second browser interface element comprises a
second browser window.
35. A computing device comprising: at least one physical memory
device to store: an application; a browser interface; and
connection management logic; and one or more processors coupled
with the at least one physical memory device, the one or more
processors configurable to execute the browser interface and the
connection management logic to receive a call to establish a first
subscription channel with a server computing device, establish a
session connection between the client computing device and the
server computing device, comprising establishing the first
subscription channel between the first application page and the
server computing device, receive a second call to establish a
second subscription channel with the server computing device,
establish the second subscription channel between the second
application page and the server computing device and manage a
sharing of-data transfers with the server computing device over the
first subscription channel and data transfers with the server
computing device over the second subscription channel via the
session connection, wherein the first subscription channel
comprises a channel between a first application page operating in a
first browser interface element wherein the second subscription
channel comprises a channel between a second application page
operating in a second browser interface element and the first
subscription channel is different from the second subscription
channel.
36. The computing device of claim 35, wherein the connection
management logic transfers first data between the client computing
device and the server computing device over the first subscription
channel via the session connection and transfers second data
between the client computing device and the server computing device
over the second subscription channel via the session
connection.
37. The computing device of claim 36, wherein the call to establish
the first subscription channel is received from a first browser
interface element and the second call to establish the second
subscription channel is received from a second browser interface
element.
38. The computing device of claim 37, wherein the connection
management logic manages the sharing of the session connection by
multiplexing data transfers between the first subscription channel
and the second subscription channel via the session connection.
39. The computing device of claim 37, wherein the browser interface
comprises a shared interface component, and wherein the connection
management logic manages the sharing of the session connection via
the shared interface component.
40. The computing device of claim 37, wherein the browser interface
comprises a dedicated worker component, and wherein the connection
management logic manages the sharing of the session connection via
one or more of the dedicated worker components.
Description
CROSS-REFERENCE
[0001] This application is a continuation of application Ser. No.
16/139,988, filed Sep. 24, 2018, the entire contents of which are
hereby incorporated herein by reference.
COPYRIGHT NOTICE
[0002] A portion of the disclosure of this patent document contains
material which is subject to copyright protection. The copyright
owner has no objection to the facsimile reproduction by anyone of
the patent document or the patent disclosure, as it appears in the
Patent and Trademark Office patent file or records, but otherwise
reserves all copyright rights whatsoever.
TECHNICAL FIELD
[0003] One or more implementations relate generally to data
management and, more specifically, to facilitating communication
between a client and a server database.
BACKGROUND
[0004] Web services (or application services) are services that are
made available from a business's Web server for Web users or other
Web-connected programs. Providers of Web services are generally
known as application service providers, and often provide one or
more web applications that are delivered over the Internet via a
browser interface at a client. In many instances a client may
access a service via one or more application pages using the
browser interface. However, an attempt to simultaneously establish
multiple client-server interfaces for the same application page via
different tabs (or windows) in the same browser interface may
result in performance issues.
BRIEF DESCRIPTION OF THE DRAWINGS
[0005] In the following drawings like reference numbers are used to
refer to like elements. Although the following figures depict
various examples, one or more implementations are not limited to
the examples depicted in the figures.
[0006] FIG. 1 illustrates one embodiment of a system;
[0007] FIG. 2 illustrates a connection session management mechanism
according to one embodiment;
[0008] FIG. 3 illustrates one embodiment of a programming model for
a connection session management mechanism;
[0009] FIG. 4A illustrates one embodiment of an implementation of a
connection management mechanism;
[0010] FIG. 4B illustrates another embodiment of an implementation
of a connection management mechanism;
[0011] FIG. 5 is a flow diagram illustrating one embodiment of
connection management process;
[0012] FIG. 6 is a timing diagram illustrating one embodiment of
connection management process;
[0013] FIG. 7 illustrates a computer system according to one
embodiment;
[0014] FIG. 8 illustrates an environment wherein an on-demand
database service might be used according to one embodiment; and
[0015] FIG. 9 illustrates elements of environment of FIG. 8 and
various possible interconnections between these elements according
to one embodiment.
DETAILED DESCRIPTION
[0016] In the following description, numerous specific details are
set forth. However, embodiments of the invention may be practiced
without these specific details. In other instances, well-known
structures and techniques have not been shown in detail in order
not to obscure the understanding of this description.
[0017] Methods and systems are provided for managing a single
client-server session connection to subscribe to client channels
and subscriptions from multiple browser tabs and windows.
[0018] It is contemplated that embodiments and their
implementations are not merely limited to multi-tenant database
system ("MTDBS") and can be used in other environments, such as a
client-server system, a mobile device, a personal computer ("PC"),
a web services environment, etc. However, for the sake of brevity
and clarity, throughout this document, embodiments are described
with respect to a multi-tenant database system, such as
Salesforce.com.RTM., which is to be regarded as an example of an
on-demand services environment. Other on-demand services
environments include Salesforce.RTM. Exact Target Marketing
Cloud.TM..
[0019] As used herein, a term multi-tenant database system refers
to those systems in which various elements of hardware and software
of the database system may be shared by one or more customers. For
example, a given application server may simultaneously process
requests for a great number of customers, and a given database
table may store rows for a potentially much greater number of
customers. As used herein, the term query plan refers to a set of
steps used to access information in a database system.
[0020] Embodiments are described with reference to an embodiment in
which techniques for facilitating management of data in an
on-demand services environment are implemented in a system having
an application server providing a front end for an on-demand
database service capable of supporting multiple tenants,
embodiments are not limited to multi-tenant databases nor
deployment on application servers. Embodiments may be practiced
using other database architectures, i.e., ORACLE.RTM., DB2.RTM. by
IBM and the like without departing from the scope of the
embodiments claimed.
[0021] FIG. 1 illustrates a system 100 having a computing device
according to one embodiment. In one embodiment, computing device
120 includes a host server computer serving a host machine. The
term "user" may refer to a system user, such as (without
limitation) a software/application developer, a system
administrator, a database administrator, an information technology
professional, a program manager, product manager, etc. The term
"user" may further refer to an end-user, such as (without
limitation) one or more of customer organizations 121A-N and/or
their representatives (e.g., individuals or groups working on
behalf of one or more of customer organizations 121A-N), such as a
salesperson, a sales manager, a product manager, an accountant, a
director, an owner, a president, a system administrator, a computer
programmer, an information technology ("IT") representative,
etc.
[0022] In one embodiment, computing device 120 may serve as a
service provider core (e.g., Salesforce.com.RTM. core) in
communication with one or more database(s) 140, one or more client
computers 130A-N, over one or more network(s) 135, and any number
and type of dedicated nodes. Computing device 120 may include
(without limitation) server computers (e.g., cloud server
computers, etc.), desktop computers, cluster-based computers,
set-top boxes (e.g., Internet-based cable television set-top boxes,
etc.), etc. Computing device 120 includes an operating system
("OS") 106 serving as an interface between one or more
hardware/physical resources of computing device 120 and one or more
client devices 130A-130N, etc. Computing device 120 further
includes processor(s) 102, memory 104, input/output ("I/O") sources
108, such as touchscreens, touch panels, touch pads, virtual or
regular keyboards, virtual or regular mice, etc.
[0023] In one embodiment, host organization 101 may further employ
a production environment that is communicably interfaced with
client devices 130A-N through host organization 101. Client devices
130A-N may include (without limitation) customer organization-based
server computers, desktop computers, laptop computers, mobile
computing devices, such as smartphones, tablet computers, personal
digital assistants, e-readers, media Internet devices, smart
televisions, television platforms, wearable devices (e.g., glasses,
watches, bracelets, smartcards, jewelry, clothing items, etc.),
media players, global positioning system-based navigation systems,
cable setup boxes, etc.
[0024] In one embodiment, the illustrated multi-tenant database
system 150 includes database(s) 140 to store (without limitation)
information, relational tables, datasets, and underlying database
records having tenant and user data therein on behalf of customer
organizations 121A-N (e.g., tenants of multi-tenant database system
150 or their affiliated users). In alternative embodiments, a
client-server computing architecture may be utilized in place of
multi-tenant database system 150, or alternatively, a computing
grid, or a pool of work servers, or some combination of hosted
computing architectures may be utilized to carry out the
computational workload and processing that is expected of host
organization 101.
[0025] The illustrated multi-tenant database system 150 is shown to
include one or more of underlying hardware, software, and logic
elements 145 that implement, for example, database functionality
and a code execution environment within host organization 101. In
accordance with one embodiment, multi-tenant database system 150
further implements databases 140 to service database queries and
other data interactions with the databases 140. In one embodiment,
hardware, software, and logic elements 145 of multi-tenant database
system 150 and its other elements, such as a distributed file
store, a query interface, etc., may be separate and distinct from
customer organizations (121A-121N) which utilize the services
provided by host organization 101 by communicably interfacing with
host organization 101 via network(s) 135 (e.g., cloud network, the
Internet, etc.). In such a way, host organization 101 may implement
on-demand services, on-demand database services, cloud computing
services, etc., to subscribing customer organizations
121A-121N.
[0026] In some embodiments, host organization 101 receives input
and other requests from a plurality of customer organizations
121A-N over one or more networks 135; for example, incoming search
queries, database queries, application programming interface
("API") requests, interactions with displayed graphical user
interfaces and displays at client devices 130A-N, or other inputs
may be received from customer organizations 121A-N to be processed
against multi-tenant database system 150 as queries via a query
interface and stored at a distributed file store, pursuant to which
results are then returned to an originator or requestor, such as a
user of client devices 130A-N at any of customer organizations
121A-N.
[0027] As aforementioned, in one embodiment, each customer
organization 121A-N is an entity selected from a group consisting
of a separate and distinct remote organization, an organizational
group within host organization 101, a business partner of host
organization 101, a customer organization 121A-N that subscribes to
cloud computing services provided by host organization 101,
etc.
[0028] In one embodiment, requests are received at, or submitted
to, a web server within host organization 101. Host organization
101 may receive a variety of requests for processing by host
organization 101 and its multi-tenant database system 150. For
example, incoming requests received at the web server may specify
which services from host organization 101 are to be provided, such
as query requests, search request, status requests, database
transactions, graphical user interface requests and interactions,
processing requests to retrieve, update, or store data on behalf of
one of customer organizations 121A-N, code execution requests, and
so forth. Further, the web-server at host organization 101 may be
responsible for receiving requests from various customer
organizations 121A-N via network(s) 135 on behalf of the query
interface and for providing a web-based interface or other
graphical displays to one or more end-user client devices 130A-N or
machines originating such data requests.
[0029] Further, host organization 101 may implement a request
interface via the web server or as a stand-alone interface to
receive requests packets or other requests from the client devices
130A-N. The request interface may further support the return of
response packets or other replies and responses in an outgoing
direction from host organization 101 to one or more client devices
130A-N.
[0030] It is to be noted that any references to software codes,
data and/or metadata (e.g., Customer Relationship Model ("CRM")
data and/or metadata, etc.), tables (e.g., custom object table,
unified index tables, description tables, etc.), computing devices
(e.g., server computers, desktop computers, mobile computers, such
as tablet computers, smartphones, etc.), software development
languages, applications, and/or development tools or kits (e.g.,
Force.com.RTM., Force.com Apex.TM. code, JavaScript.TM.,
jQuery.TM., Developerforce.TM., Visualforce.TM., Service Cloud
Console Integration Toolkit.TM. ("Integration Toolkit" or
"Toolkit"), Platform on a Service.TM. ("PaaS"), Chatter.RTM.
Groups, Sprint Planner.RTM., MS Project.RTM., etc.), domains (e.g.,
Google.RTM., Facebook.RTM., LinkedIn.RTM., Skype.RTM., etc.), etc.,
discussed in this document are merely used as examples for brevity,
clarity, and ease of understanding and that embodiments are not
limited to any particular number or type of data, metadata, tables,
computing devices, techniques, programming languages, software
applications, software development tools/kits, etc.
[0031] It is to be noted that terms like "node", "computing node",
"server", "server device", "cloud computer", "cloud server", "cloud
server computer", "machine", "host machine", "device", "computing
device", "computer", "computing system", "multi-tenant on-demand
data system", "multi-tenant database system" and the like, may be
used interchangeably throughout this document. It is to be further
noted that terms like "code", "software code", "application",
"software application", "program", "software program", "package",
"software code", "code", and "software package" may be used
interchangeably throughout this document. Moreover, terms like
"job", "input", "request", and "message" may be used
interchangeably throughout this document.
[0032] FIG. 2 illustrates one embodiment of a client computing
device 130. In this embodiment, computing device 130 is a mobile
device hosting an application 210 that accesses multi-tenant
database system 150 at host organization 101 via requests. However
other embodiments may feature other types of computing devices
(e.g., desktop, tablet, etc.). According to one embodiment,
application 210 maintains a local copy of data stored in customer
organizations 121A-N pertinent to the particular customer
organization 121 to which computing device 130 is associated.
[0033] In a further embodiment, application 210 includes one or
more application pages 211 having custom layouts designed by a user
of computing device 130. In such an embodiment, an application page
211 includes one or more components to facilitate the transfer of
data (e.g., events and messages) between computing device 130 and
server 120. In a further embodiment, application pages 211
comprises Lightning.RTM. pages, developed by Salesforce.com.RTM.,
including one or more Lightning.RTM. components. Additionally,
application 210 includes a browser 220 implemented to access
application pages 211.
[0034] As discussed above, performance issues may occur during an
attempt to establish multiple connections to a server via a
browser. For instance, an application page operating in a browser
may be configured to receive notifications from the server via a
session connection, while a component of the same application page
in the browser uses a separate session connection to communicate
with the server. Such a scenario may result in a "1 connection per
browser" constraint configured at the server, which results in
receiving a multiple clients detected response from the server.
Upon transmission of the response, the server expects clients to
connect within a timeout value. However the server expects clients
to connect within an interval value (e.g., if the interval value is
greater than 0).
[0035] In instances in which notifications are disabled, the server
may also detect multiple-clients usage in situations in which an
application page having one or more of the same application
components is opened in multiple browser tabs (or windows). As a
result, the server expects the client to connect every 2 seconds
simulating "short-polling" behavior. A further limitation is that
some browsers are limited to two connections per domain, which
severely affects page loading performance.
[0036] According to one embodiment, application 210 includes a
connection management mechanism 212 to manage a single session
connection between client 130 and server 120 (e.g., server side
subscription) for multiple client channel subscriptions. In such an
embodiment, management mechanism 212 manages channel subscriptions
from application page 211 components operating in one or more
browser interface elements (or contexts) (e.g., tabs, windows,
portals, etc.) subscribing to the same topic, while maintaining a
single session connection with server 120 to transfer messages
between the application pages 211 and server 120. In a further
embodiment, connection management mechanism 212 performs a
multiplexing of events and messages for the subscription channels
to enable data transfers with server 120 via the single session
connection.
[0037] As shown in FIG. 2, connection management mechanism 212
includes session connection module 215 and connection manager 218.
Session connection module 215 establishes a session connection to
server 120 via a defined protocol. According to one embodiment,
session connection module 215 is implemented using a Comet web
application (e.g., CometD) to establish session connections with
server 120 via a scalable WebSocket and HTTP based event and
message routing interface. Connection manager 218 manages
communications via session connection module 215 for one or more
subscription channels initiated by application pages 211 operating
in browser 220.
[0038] According to one embodiment, connection manager 218 is
implemented using EmpJs, which is a javascript library that
controls (or wraps) the Comet application to manage the session
connection with server 120. FIG. 3 illustrates one embodiment, of a
programming model implemented by connection manager 218 to manage a
connection with a server 120. As shown in FIG. 3, the programming
model establishes a connection with the server and reestablishes
the connection upon a failure.
[0039] In one embodiment, connection manager 218 manages the
session connection using a Shared Worker 222 component of browser
220 to operate session connection module 215. In such an embodiment
an application page 211 accesses connection manager 218 to
subscribe to one or more channels. FIG. 4A illustrates one
embodiment of a connection management mechanism flow 212 using a
shared worker 222. As shown in FIG. 4A, multiple browser tabs 405
(e.g., 405 (A) and 405 (B)) each include a page 211 and alert
function 412 that establish subscription channels to shared worker
222 via connection manager 215. Shared worker 222 is in turn used
to manage session connection module 218 to establish a session
connection with a cloud server 415. As a result, connection manager
218, on behalf of a tab 405, accesses shared worker 222 for the
establishing of a connection via session connection module 215 for
communication with server 120.
[0040] In some embodiments, browser 220 may not support a shared
worker 222 function (FIG. 2). In such embodiments, connection
manager 218 implements a dedicated worker component 224 in browser
220 to perform a dedicated worker and leader election. FIG. 4B
illustrates another embodiment of a connection management mechanism
flow 212 using dedicated workers 224. In one embodiment, dedicated
worker component 224 performs a leader election using a Raft
consensus algorithm. As a result, each browser tab 405 generates a
dedicated worker 224 to run leader election.
[0041] Once a leader tab 405 is elected (e.g., tab 405(A)), the
leader begins to transmit heartbeats to other tabs 405.
Additionally, the leader tab 405 manages the session connection via
module 218, while other tabs 405 transmit subscribe/unsubscribe
calls to the leader tab 405. According to one embodiment, the
heartbeat messages, events, and session subscribe/unsubscribe
request messages are communicated via local storage 420. In such an
embodiment, the leader tab 405 is used as a proxy since the
dedicated workers 224 cannot directly access local storage 420.
[0042] FIG. 5 is a flow diagram of a method 500 for facilitating
management of a single connection of a client device with a server
according to one embodiment. Method 500 may be performed by
processing logic that may comprise hardware (e.g., circuitry,
dedicated logic, programmable logic, etc.), software (such as
instructions run on a processing device), or a combination thereof.
The processes of method 500 are illustrated in linear sequences for
brevity and clarity in presentation; however, it is contemplated
that any number of them can be performed in parallel,
asynchronously, or in different orders. Further, for brevity,
clarity, and ease of understanding, many of the components and
processes described with respect to FIGS. 1-4 may not be repeated
or discussed hereafter.
[0043] Method 500 begins at processing block 510, where a
subscriber call to establish a subscription channel with a server
is received (e.g., from an application page in a browser tab or
window). At processing block 520, a session connection is
established between the client and the server based on the
subscriber request. As a result, the subscription channel is used
to communicate messages and events between the client and server
via the established session connection, processing block 530. At
decision block 540, a determination is made as to whether a
subsequent subscriber call to establish a subscription channel has
been received (e.g., from an application page in a different tab or
window, or different portal on the same application page). If not
control is returned to decision block 540 for continued monitoring
to determine whether another call has been received.
[0044] If at decision block 540, a determination is made that a
subsequent subscriber call has been received, a sharing of the
session connection between the two subscription channels is
managed, processing block 550. As a result, the established session
connection is used by the subsequent subscription channel to
communicate with the server. As discussed above, events and
messages to/from the subscription channels are multiplexed for
client-server transfers via the session connection. Subsequently
control is returned to decision block 540 to determine whether
another request has been received.
[0045] FIGS. 6 is a timing diagram illustrating one embodiment of
connection management process performed by connection management
mechanism 210. As shown in FIG. 6, the process starts at ti where a
subscription call (e.g., Subscribe/event/dbTest_e) is received at
connection management mechanism 210 from browser tab 1, at t.sub.2,
connection management mechanism 210 makes a call (e.g.,
/meta/subscribe(/event/dbTest_e)) to the server to establish a
connection session. As a result, an application running at tab 1
may exchange messages and events with the server. At t.sub.3,
connection management mechanism 210 receives a subsequent
subscription call from tab 2. Since connection session has already
been established, the session connection is managed to enable an
application running at tab 2 to exchange messages and events with
the server via a multiplexing with messages and events for the
application running at tab 1.
[0046] In some embodiments, the call from tab 2 may operate
differently than the first call in instances in which application
page 211 components request all events to run data analysis on the
client-side. In such instances, all of the available events may not
be received. In such an embodiment, the application page may
unsubscribe from the channel when the focus leaves the tab (or
window). Subsequently, the clients may re-subscribe to a channel
upon a refocus. In another embodiment, the client always subscribe
to a channel with -2 and implement caching and re-binning on the
client-side to deliver events to the subscribers with different
replay identifiers.
[0047] In yet another embodiment, the client encodes a replayId as
part of the channel name (e.g., ''/event/dbTest_e?replayId=-2; or
''/event/dbTest_e?replayId=123), and session connection module 215
treats the two channels as two different channels and makes two
separate /meta/subscribe calls. As a result, the server would
manage two session connections (or subscriptions). In still a
further embodiment, a dynamic multiplexed stream may be
implemented. In such an embodiment, a virtual channel is created
and connection session module 215 is used to publish an API to
encode the subscribe calls. Accordingly, the server handles all
conduit subscriptions and multiplexes events from all the
subscriptions onto the session connection, connection manager 218
performs de-multiplexing.
[0048] FIG. 7 illustrates a diagrammatic representation of a
machine 900 in the exemplary form of a computer system, in
accordance with one embodiment, within which a set of instructions,
for causing the machine 900 to perform any one or more of the
methodologies discussed herein, may be executed. Machine 900 is the
same as or similar to computing devices 120, 130A-N of FIG. 1. In
alternative embodiments, the machine may be connected (e.g.,
networked) to other machines in a network (such as host machine 120
connected with client machines 130A-N over network(s) 135 of FIG.
1), such as a cloud-based network, Internet of Things (IoT) or
Cloud of Things (CoT), a Local Area Network (LAN), a Wide Area
Network (WAN), a Metropolitan Area Network (MAN), a Personal Area
Network (PAN), an intranet, an extranet, or the Internet. The
machine may operate in the capacity of a server or a client machine
in a client-server network environment, or as a peer machine in a
peer-to-peer (or distributed) network environment or as a server or
series of servers within an on-demand service environment,
including an on-demand environment providing multi-tenant database
storage services. Certain embodiments of the machine may be in the
form of a personal computer (PC), a tablet PC, a set-top box (STB),
a Personal Digital Assistant (PDA), a cellular telephone, a web
appliance, a server, a network router, switch or bridge, computing
system, or any machine capable of executing a set of instructions
(sequential or otherwise) that specify actions to be taken by that
machine. Further, while only a single machine is illustrated, the
term "machine" shall also be taken to include any collection of
machines (e.g., computers) that individually or jointly execute a
set (or multiple sets) of instructions to perform any one or more
of the methodologies discussed herein.
[0049] The exemplary computer system 900 includes a processor 902,
a main memory 504 (e.g., read-only memory (ROM), flash memory,
dynamic random access memory (DRAM) such as synchronous DRAM
(SDRAM) or Rambus DRAM (RDRAM), etc., static memory such as flash
memory, static random access memory (SRAM), volatile but high-data
rate RAM, etc.), and a secondary memory 918 (e.g., a persistent
storage device including hard disk drives and persistent
multi-tenant data base implementations), which communicate with
each other via a bus 930. Main memory 904 includes emitted
execution data 924 (e.g., data emitted by a logging framework) and
one or more trace preferences 923 which operate in conjunction with
processing logic 926 and processor 902 to perform the methodologies
discussed herein.
[0050] Processor 902 represents one or more general-purpose
processing devices such as a microprocessor, central processing
unit, or the like. More particularly, the processor 902 may be a
complex instruction set computing (CISC) microprocessor, reduced
instruction set computing (RISC) microprocessor, very long
instruction word (VLIW) microprocessor, processor implementing
other instruction sets, or processors implementing a combination of
instruction sets. Processor 902 may also be one or more
special-purpose processing devices such as an application specific
integrated circuit (ASIC), a field programmable gate array (FPGA),
a digital signal processor (DSP), network processor, or the like.
Processor 902 is configured to execute the processing logic 926 for
performing the operations as described with reference to FIG. 1 and
other Figures discussed herein.
[0051] The computer system 900 may further include a network
interface card 908. The computer system 900 also may include a user
interface 910 (such as a video display unit, a liquid crystal
display (LCD), or a cathode ray tube (CRT)), an alphanumeric input
device 912 (e.g., a keyboard), a cursor control device 914 (e.g., a
mouse), and a signal generation device 916 (e.g., an integrated
speaker). The computer system 900 may further include peripheral
device 936 (e.g., wireless or wired communication devices, memory
devices, storage devices, audio processing devices, video
processing devices, etc. The computer system 900 may further
include a Hardware based API logging framework 934 capable of
executing incoming requests for services and emitting execution
data responsive to the fulfillment of such incoming requests.
[0052] The secondary memory 918 may include a machine-readable
storage medium (or more specifically a machine-accessible storage
medium) 931 on which is stored one or more sets of instructions
(e.g., software 922) embodying any one or more of the methodologies
as described with reference to FIG. 1, respectively, and other
figures discussed herein. The software 522 may also reside,
completely or at least partially, within the main memory 904 and/or
within the processor 902 during execution thereof by the computer
system 900, the main memory 904 and the processor 902 also
constituting machine-readable storage media. The software 922 may
further be transmitted or received over a network 920 via the
network interface card 908. The machine-readable storage medium 931
may include transitory or non-transitory machine-readable storage
media.
[0053] Portions of various embodiments may be provided as a
computer program product, which may include a computer-readable
medium having stored thereon computer program instructions, which
may be used to program a computer (or other electronic devices) to
perform a process according to the embodiments. The
machine-readable medium may include, but is not limited to, floppy
diskettes, optical disks, compact disk read-only memory (CD-ROM),
and magneto-optical disks, ROM, RAM, erasable programmable
read-only memory (EPROM), electrically EPROM (EEPROM), magnet or
optical cards, flash memory, or other type of
media/machine-readable medium suitable for storing electronic
instructions.
[0054] The techniques shown in the figures can be implemented using
code and data stored and executed on one or more electronic devices
(e.g., an end station, a network element). Such electronic devices
store and communicate (internally and/or with other electronic
devices over a network) code and data using computer-readable
media, such as non-transitory computer-readable storage media
(e.g., magnetic disks; optical disks; random access memory; read
only memory; flash memory devices; phase-change memory) and
transitory computer-readable transmission media (e.g., electrical,
optical, acoustical or other form of propagated signals--such as
carrier waves, infrared signals, digital signals). In addition,
such electronic devices typically include a set of one or more
processors coupled to one or more other components, such as one or
more storage devices (non-transitory machine-readable storage
media), user input/output devices (e.g., a keyboard, a touchscreen,
and/or a display), and network connections. The coupling of the set
of processors and other components is typically through one or more
busses and bridges (also termed as bus controllers). Thus, the
storage device of a given electronic device typically stores code
and/or data for execution on the set of one or more processors of
that electronic device. Of course, one or more parts of an
embodiment may be implemented using different combinations of
software, firmware, and/or hardware.
[0055] FIG. 8 illustrates a block diagram of an environment 1010
wherein an on-demand database service might be used. Environment
1010 may include user systems 1012, network 1014, system 1016,
processor system 1017, application platform 618, network interface
1020, tenant data storage 1022, system data storage 1024, program
code 1026, and process space 1028. In other embodiments,
environment 1010 may not have all of the components listed and/or
may have other elements instead of, or in addition to, those listed
above.
[0056] Environment 1010 is an environment in which an on-demand
database service exists. User system 1012 may be any machine or
system that is used by a user to access a database user system. For
example, any of user systems 1012 can be a handheld computing
device, a mobile phone, a laptop computer, a workstation, and/or a
network of computing devices. As illustrated in herein FIG. 8 (and
in more detail in FIG. 9) user systems 1012 might interact via a
network 1014 with an on-demand database service, which is system
1016.
[0057] An on-demand database service, such as system 1016, is a
database system that is made available to outside users that do not
need to necessarily be concerned with building and/or maintaining
the database system, but instead may be available for their use
when the users need the database system (e.g., on the demand of the
users). Some on-demand database services may store information from
one or more tenants stored into tables of a common database image
to form a multi-tenant database system (MTS). Accordingly,
"on-demand database service 1016" and "system 1016" will be used
interchangeably herein. A database image may include one or more
database objects. A relational database management system (RDMS) or
the equivalent may execute storage and retrieval of information
against the database object(s). Application platform 1018 may be a
framework that allows the applications of system 1016 to run, such
as the hardware and/or software, e.g., the operating system. In an
embodiment, on-demand database service 1016 may include an
application platform 1018 that enables creation, managing and
executing one or more applications developed by the provider of the
on-demand database service, users accessing the on-demand database
service via user systems 1012, or third party application
developers accessing the on-demand database service via user
systems 1012.
[0058] The users of user systems 1012 may differ in their
respective capacities, and the capacity of a particular user system
1012 might be entirely determined by permissions (permission
levels) for the current user. For example, where a salesperson is
using a particular user system 1012 to interact with system 1016,
that user system has the capacities allotted to that salesperson.
However, while an administrator is using that user system to
interact with system 1016, that user system has the capacities
allotted to that administrator. In systems with a hierarchical role
model, users at one permission level may have access to
applications, data, and database information accessible by a lower
permission level user, but may not have access to certain
applications, database information, and data accessible by a user
at a higher permission level. Thus, different users will have
different capabilities with regard to accessing and modifying
application and database information, depending on a user's
security or permission level.
[0059] Network 1014 is any network or combination of networks of
devices that communicate with one another. For example, network
1014 can be any one or any combination of a LAN (local area
network), WAN (wide area network), telephone network, wireless
network, point-to-point network, star network, token ring network,
hub network, or other appropriate configuration. As the most common
type of computer network in current use is a TCP/IP (Transfer
Control Protocol and Internet Protocol) network, such as the global
internetwork of networks often referred to as the "Internet" with a
capital "I," that network will be used in many of the examples
herein. However, it should be understood that the networks that one
or more implementations might use are not so limited, although
TCP/IP is a frequently implemented protocol.
[0060] User systems 1012 might communicate with system 1016 using
TCP/IP and, at a higher network level, use other common Internet
protocols to communicate, such as HTTP, FTP, AFS, WAP, etc. In an
example where HTTP is used, user system 1012 might include an HTTP
client commonly referred to as a "browser" for sending and
receiving HTTP messages to and from an HTTP server at system 1016.
Such an HTTP server might be implemented as the sole network
interface between system 1016 and network 1014, but other
techniques might be used as well or instead. In some
implementations, the interface between system 1016 and network 1014
includes load-sharing functionality, such as round-robin HTTP
request distributors to balance loads and distribute incoming HTTP
requests evenly over a plurality of servers. At least as for the
users that are accessing that server, each of the plurality of
servers has access to the MTS' data; however, other alternative
configurations may be used instead.
[0061] In one embodiment, system 1016, shown in FIG. 8, implements
a web-based customer relationship management (CRM) system. For
example, in one embodiment, system 616 includes application servers
configured to implement and execute CRM software applications as
well as provide related data, code, forms, webpages and other
information to and from user systems 1012 and to store to, and
retrieve from, a database system related data, objects, and Webpage
content. With a multi-tenant system, data for multiple tenants may
be stored in the same physical database object, however, tenant
data typically is arranged so that data of one tenant is kept
logically separate from that of other tenants so that one tenant
does not have access to another tenant's data, unless such data is
expressly shared. In certain embodiments, system 1016 implements
applications other than, or in addition to, a CRM application. For
example, system 1016 may provide tenant access to multiple hosted
(standard and custom) applications, including a CRM application.
User (or third party developer) applications, which may or may not
include CRM, may be supported by the application platform 618,
which manages creation, storage of the applications into one or
more database objects and executing of the applications in a
virtual machine in the process space of the system 1016.
[0062] One arrangement for elements of system 1016 is shown in FIG.
8, including a network interface 1020, application platform 1018,
tenant data storage 1022 for tenant data 1023, system data storage
1024 for system data 1025 accessible to system 1016 and possibly
multiple tenants, program code 1026 for implementing various
functions of system 1016, and a process space 1028 for executing
MTS system processes and tenant-specific processes, such as running
applications as part of an application hosting service. Additional
processes that may execute on system 1016 include database-indexing
processes.
[0063] Several elements in the system shown in FIG. 8 include
conventional, well-known elements that are explained only briefly
here. For example, each user system 1012 could include a desktop
personal computer, workstation, laptop, PDA, cell phone, or any
wireless access protocol (WAP) enabled device or any other
computing device capable of interfacing directly or indirectly to
the Internet or other network connection. User system 1012
typically runs an HTTP client, e.g., a browsing program, such as
Microsoft's Internet Explorer browser, Netscape's Navigator
browser, Opera's browser, or a WAP-enabled browser in the case of a
cell phone, PDA or other wireless device, or the like, allowing a
user (e.g., subscriber of the multi-tenant database system) of user
system 1012 to access, process and view information, pages and
applications available to it from system 1016 over network 1014.
User system 1012 further includes Mobile OS (e.g., iOS.RTM. by
Apple.RTM., Android.RTM., WebOS.RTM. by Palm.RTM., etc.). Each user
system 1012 also typically includes one or more user interface
devices, such as a keyboard, a mouse, trackball, touch pad, touch
screen, pen or the like, for interacting with a graphical user
interface (GUI) provided by the browser on a display (e.g., a
monitor screen, LCD display, etc.) in conjunction with pages,
forms, applications and other information provided by system 1016
or other systems or servers. For example, the user interface device
can be used to access data and applications hosted by system 1016,
and to perform searches on stored data, and otherwise allow a user
to interact with various GUI pages that may be presented to a user.
As discussed above, embodiments are suitable for use with the
Internet, which refers to a specific global internetwork of
networks. However, it should be understood that other networks can
be used instead of the Internet, such as an intranet, an extranet,
a virtual private network (VPN), a non-TCP/IP based network, any
LAN or WAN or the like.
[0064] According to one embodiment, each user system 1012 and all
of its components are operator configurable using applications,
such as a browser, including computer code run using a central
processing unit such as an Intel Core.RTM. processor or the like.
Similarly, system 1016 (and additional instances of an MTS, where
more than one is present) and all of their components might be
operator configurable using application(s) including computer code
to run using a central processing unit such as processor system
1017, which may include an Intel Pentium.RTM. processor or the
like, and/or multiple processor units. A computer program product
embodiment includes a machine-readable storage medium (media)
having instructions stored thereon/in which can be used to program
a computer to perform any of the processes of the embodiments
described herein. Computer code for operating and configuring
system 1016 to intercommunicate and to process webpages,
applications and other data and media content as described herein
are preferably downloaded and stored on a hard disk, but the entire
program code, or portions thereof, may also be stored in any other
volatile or non-volatile memory medium or device as is well known,
such as a ROM or RAM, or provided on any media capable of storing
program code, such as any type of rotating media including floppy
disks, optical discs, digital versatile disk (DVD), compact disk
(CD), microdrive, and magneto-optical disks, and magnetic or
optical cards, nanosystems (including molecular memory ICs), or any
type of media or device suitable for storing instructions and/or
data. Additionally, the entire program code, or portions thereof,
may be transmitted and downloaded from a software source over a
transmission medium, e.g., over the Internet, or from another
server, as is well known, or transmitted over any other
conventional network connection as is well known (e.g., extranet,
VPN, LAN, etc.) using any communication medium and protocols (e.g.,
TCP/IP, HTTP, HTTPS, Ethernet, etc.) as are well known. It will
also be appreciated that computer code for implementing embodiments
can be implemented in any programming language that can be executed
on a client system and/or server or server system such as, for
example, C, C++, HTML, any other markup language, Java.TM.,
JavaScript, ActiveX, any other scripting language, such as
VBScript, and many other programming languages as are well known
may be used. (Java.TM. is a trademark of Sun Microsystems,
Inc.).
[0065] According to one embodiment, each system 1016 is configured
to provide webpages, forms, applications, data and media content to
user (client) systems 1012 to support the access by user systems
1012 as tenants of system 1016. As such, system 1016 provides
security mechanisms to keep each tenant's data separate unless the
data is shared. If more than one MTS is used, they may be located
in close proximity to one another (e.g., in a server farm located
in a single building or campus), or they may be distributed at
locations remote from one another (e.g., one or more servers
located in city A and one or more servers located in city B). As
used herein, each MTS could include one or more logically and/or
physically connected servers distributed locally or across one or
more geographic locations. Additionally, the term "server" is meant
to include a computer system, including processing hardware and
process space(s), and an associated storage system and database
application (e.g., OODBMS or RDBMS) as is well known in the art. It
should also be understood that "server system" and "server" are
often used interchangeably herein. Similarly, the database object
described herein can be implemented as single databases, a
distributed database, a collection of distributed databases, a
database with redundant online or offline backups or other
redundancies, etc., and might include a distributed database or
storage network and associated processing intelligence.
[0066] FIG. 9 also illustrates environment 1010. However, in FIG. 9
elements of system 1016 and various interconnections in an
embodiment are further illustrated. FIG. 9 shows that user system
1012 may include processor system 1012A, memory system 1012B, input
system 1012C, and output system 1012D. FIG. 9 shows network 1014
and system 1016. FIG. 9 also shows that system 1016 may include
tenant data storage 1022, tenant data 1023, system data storage
1024, system data 1025, User Interface (UI) 1130, Application
Program Interface (API) 1132, PL/SOQL 1134, save routines 1136,
application setup mechanism 1138, applications servers
1100.sub.1-1100.sub.N, system process space 1102, tenant process
spaces 1104, tenant management process space 1110, tenant storage
area 1112, user storage 1114, and application metadata 1116. In
other embodiments, environment 1010 may not have the same elements
as those listed above and/or may have other elements instead of, or
in addition to, those listed above.
[0067] User system 1012, network 1014, system 1016, tenant data
storage 1022, and system data storage 1024 were discussed above in
FIG. 8. Regarding user system 1012, processor system 1012A may be
any combination of one or more processors. Memory system 1012B may
be any combination of one or more memory devices, short term,
and/or long term memory. Input system 1012C may be any combination
of input devices, such as one or more keyboards, mice, trackballs,
scanners, cameras, and/or interfaces to networks. Output system
1012D may be any combination of output devices, such as one or more
monitors, printers, and/or interfaces to networks. As shown by FIG.
9, system 1016 may include a network interface 1020 (of FIG. 8)
implemented as a set of HTTP application servers 1100, an
application platform 1018, tenant data storage 1022, and system
data storage 1024. Also shown is system process space 1102,
including individual tenant process spaces 1104 and a tenant
management process space 1110. Each application server 1100 may be
configured to tenant data storage 1022 and the tenant data 1023
therein, and system data storage 1024 and the system data 1025
therein to serve requests of user systems 1012. The tenant data
1023 might be divided into individual tenant storage areas 1112,
which can be either a physical arrangement and/or a logical
arrangement of data. Within each tenant storage area 1112, user
storage 1114 and application metadata 1116 might be similarly
allocated for each user. For example, a copy of a user's most
recently used (MRU) items might be stored to user storage 1114.
Similarly, a copy of MRU items for an entire organization that is a
tenant might be stored to tenant storage area 1112. A UI 1130
provides a user interface and an API 71132 provides an application
programmer interface to system 1016 resident processes to users
and/or developers at user systems 1012. The tenant data and the
system data may be stored in various databases, such as one or more
Oracle.TM. databases.
[0068] Application platform 1018 includes an application setup
mechanism 1138 that supports application developers' creation and
management of applications, which may be saved as metadata into
tenant data storage 1022 by save routines 1136 for execution by
subscribers as one or more tenant process spaces 1104 managed by
tenant management process 1110 for example. Invocations to such
applications may be coded using PL/SOQL 1134 that provides a
programming language style interface extension to API 1132. A
detailed description of some PL/SOQL language embodiments is
discussed in commonly owned U.S. Pat. No. 7,730,478 entitled,
"Method and System for Allowing Access to Developed Applicants via
a Multi-Tenant Database On-Demand Database Service", issued Jun. 1,
2010 to Craig Weissman, which is incorporated in its entirety
herein for all purposes. Invocations to applications may be
detected by one or more system processes, which manage retrieving
application metadata 1116 for the subscriber making the invocation
and executing the metadata as an application in a virtual
machine.
[0069] Each application server 1100 may be communicably coupled to
database systems, e.g., having access to system data 1025 and
tenant data 1023, via a different network connection. For example,
one application server 1100.sub.1 might be coupled via the network
1014 (e.g., the Internet), another application server
1100.sub.N-1might be coupled via a direct network link, and another
application server 1100.sub.N might be coupled by yet a different
network connection. Transfer Control Protocol and Internet Protocol
(TCP/IP) are typical protocols for communicating between
application servers 1100 and the database system. However, it will
be apparent to one skilled in the art that other transport
protocols may be used to optimize the system depending on the
network interconnect used.
[0070] In certain embodiments, each application server 1100 is
configured to handle requests for any user associated with any
organization that is a tenant. Because it is desirable to be able
to add and remove application servers from the server pool at any
time for any reason, there is preferably no server affinity for a
user and/or organization to a specific application server 1100. In
one embodiment, therefore, an interface system implementing a load
balancing function (e.g., an F5 Big-IP load balancer) is
communicably coupled between the application servers 1100 and the
user systems 1012 to distribute requests to the application servers
1100. In one embodiment, the load balancer uses a least connections
algorithm to route user requests to the application servers 1100.
Other examples of load balancing algorithms, such as round robin
and observed response time, also can be used. For example, in
certain embodiments, three consecutive requests from the same user
could hit three different application servers 1100, and three
requests from different users could hit the same application server
1100. In this manner, system 1016 is multi-tenant, wherein system
1016 handles storage of, and access to, different objects, data and
applications across disparate users and organizations.
[0071] As an example of storage, one tenant might be a company that
employs a sales force where each salesperson uses system 1016 to
manage their sales process. Thus, a user might maintain contact
data, leads data, customer follow-up data, performance data, goals
and progress data, etc., all applicable to that user's personal
sales process (e.g., in tenant data storage 1022). In an example of
a MTS arrangement, since all of the data and the applications to
access, view, modify, report, transmit, calculate, etc., can be
maintained and accessed by a user system having nothing more than
network access, the user can manage his or her sales efforts and
cycles from any of many different user systems. For example, if a
salesperson is visiting a customer and the customer has Internet
access in their lobby, the salesperson can obtain critical updates
as to that customer while waiting for the customer to arrive in the
lobby.
[0072] While each user's data might be separate from other users'
data regardless of the employers of each user, some data might be
organization-wide data shared or accessible by a plurality of users
or all of the users for a given organization that is a tenant.
Thus, there might be some data structures managed by system 1016
that are allocated at the tenant level while other data structures
might be managed at the user level. Because an MTS might support
multiple tenants including possible competitors, the MTS should
have security protocols that keep data, applications, and
application use separate. Also, because many tenants may opt for
access to an MTS rather than maintain their own system, redundancy,
up-time, and backup are additional functions that may be
implemented in the MTS. In addition to user-specific data and
tenant specific data, system 1016 might also maintain system level
data usable by multiple tenants or other data. Such system level
data might include industry reports, news, postings, and the like
that are sharable among tenants.
[0073] In certain embodiments, user systems 1012 (which may be
client systems) communicate with application servers 1100 to
request and update system-level and tenant-level data from system
1016 that may require sending one or more queries to tenant data
storage 1022 and/or system data storage 1024. System 1016 (e.g., an
application server 1100 in system 1016) automatically generates one
or more SQL statements (e.g., one or more SQL queries) that are
designed to access the desired information. System data storage
1024 may generate query plans to access the requested data from the
database.
[0074] Each database can generally be viewed as a collection of
objects, such as a set of logical tables, containing data fitted
into predefined categories. A "table" is one representation of a
data object, and may be used herein to simplify the conceptual
description of objects and custom objects. It should be understood
that "table" and "object" may be used interchangeably herein. Each
table generally contains one or more data categories logically
arranged as columns or fields in a viewable schema. Each row or
record of a table contains an instance of data for each category
defined by the fields. For example, a CRM database may include a
table that describes a customer with fields for basic contact
information such as name, address, phone number, fax number, etc.
Another table might describe a purchase order, including fields for
information such as customer, product, sale price, date, etc. In
some multi-tenant database systems, standard entity tables might be
provided for use by all tenants. For CRM database applications,
such standard entities might include tables for Account, Contact,
Lead, and Opportunity data, each containing pre-defined fields. It
should be understood that the word "entity" may also be used
interchangeably herein with "object" and "table".
[0075] In some multi-tenant database systems, tenants may be
allowed to create and store custom objects, or they may be allowed
to customize standard entities or objects, for example by creating
custom fields for standard objects, including custom index fields.
U.S. patent application Ser. No. 10/817,161, filed Apr. 2, 2004,
entitled "Custom Entities and Fields in a Multi-Tenant Database
System", and which is hereby incorporated herein by reference,
teaches systems and methods for creating custom objects as well as
customizing standard objects in a multi-tenant database system. In
certain embodiments, for example, all custom entity data rows are
stored in a single multi-tenant physical table, which may contain
multiple logical tables per organization. It is transparent to
customers that their multiple "tables" are in fact stored in one
large table or that their data may be stored in the same table as
the data of other customers.
[0076] Any of the above embodiments may be used alone or together
with one another in any combination. Embodiments encompassed within
this specification may also include embodiments that are only
partially mentioned or alluded to or are not mentioned or alluded
to at all in this brief summary or in the abstract. Although
various embodiments may have been motivated by various deficiencies
with the prior art, which may be discussed or alluded to in one or
more places in the specification, the embodiments do not
necessarily address any of these deficiencies. In other words,
different embodiments may address different deficiencies that may
be discussed in the specification. Some embodiments may only
partially address some deficiencies or just one deficiency that may
be discussed in the specification, and some embodiments may not
address any of these deficiencies.
[0077] While one or more implementations have been described by way
of example and in terms of the specific embodiments, it is to be
understood that one or more implementations are not limited to the
disclosed embodiments. To the contrary, it is intended to cover
various modifications and similar arrangements as would be apparent
to those skilled in the art. Therefore, the scope of the appended
claims should be accorded the broadest interpretation so as to
encompass all such modifications and similar arrangements. It is to
be understood that the above description is intended to be
illustrative, and not restrictive.
* * * * *