KR20170032669A - Apparatus and method for providing static resources for multi-tenant - Google Patents

Apparatus and method for providing static resources for multi-tenant Download PDF

Info

Publication number
KR20170032669A
KR20170032669A KR1020150130293A KR20150130293A KR20170032669A KR 20170032669 A KR20170032669 A KR 20170032669A KR 1020150130293 A KR1020150130293 A KR 1020150130293A KR 20150130293 A KR20150130293 A KR 20150130293A KR 20170032669 A KR20170032669 A KR 20170032669A
Authority
KR
South Korea
Prior art keywords
static resource
tenant
information
resource
static
Prior art date
Application number
KR1020150130293A
Other languages
Korean (ko)
Inventor
고광현
이석준
민대홍
정목영
김기훈
양선호
Original Assignee
삼성에스디에스 주식회사
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 삼성에스디에스 주식회사 filed Critical 삼성에스디에스 주식회사
Priority to KR1020150130293A priority Critical patent/KR20170032669A/en
Publication of KR20170032669A publication Critical patent/KR20170032669A/en

Links

Images

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/50—Allocation of resources, e.g. of the central processing unit [CPU]
    • G06F9/5005—Allocation of resources, e.g. of the central processing unit [CPU] to service a request
    • G06F9/5027—Allocation of resources, e.g. of the central processing unit [CPU] to service a request the resource being a machine, e.g. CPUs, Servers, Terminals
    • G06F17/3089—
    • 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/50—Allocation of resources, e.g. of the central processing unit [CPU]
    • G06F9/5061—Partitioning or combining of resources
    • G06F9/5072—Grid computing
    • 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/50—Allocation of resources, e.g. of the central processing unit [CPU]
    • G06F9/5083—Techniques for rebalancing the load in a distributed system

Landscapes

  • Engineering & Computer Science (AREA)
  • Software Systems (AREA)
  • Theoretical Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Mathematical Physics (AREA)
  • Information Transfer Between Computers (AREA)

Abstract

The present invention provides an apparatus and method for providing static resources for multi-tenants. According to the present invention, the apparatus for providing static resources include: a request analyzer configured to receive a request message of static resources, used in configuration of a web page, from a user terminal in response to a web server providing the web page to the user terminal, and to extract information of the static resources and information of a tenant both included in the request message of the static resources; and a resource manager configured to receive the information of the static resources and the information of the tenant from the request analyzer, and to provide the static resources corresponding to the tenant to the user terminal by using the information of the static resources and the information of the tenant. Accordingly, the present invention provides a means efficiently processing static resources differently requested for each tenant.

Description

[0001] APPARATUS AND METHOD FOR PROVIDING STATIC RESOURCES FOR MULTI-TENANT [0002]

Embodiments of the present invention relate to techniques for variably providing static resources required for each tenant.

Software as a Service (SaaS) is a service delivery model that provides services to multiple tenants using one platform, and supports multi-tenants. However, conventionally, there has been a limit in implementing a branch logic for each tenant at a web page level when a service for multi-tenants is provided. In other words, conventionally, in order to process the static resources necessary for each tenant, there has been a problem that the source code must be different for each tenant at the web page level. In addition, conventionally, a static resource is provided by a web server, which increases the load on the web server when the tenant increases. Further, conventionally, when there are a plurality of web servers for each tenant, storage of all the static resources required for storage of each web server is duplicated, resulting in a storage efficiency being lowered.

Korean Published Patent Application No. 10-2012-0044516 (2012.05.08)

Embodiments of the present invention are intended to provide a means for efficiently processing static resources that are differently required by tenants.

According to an exemplary embodiment of the present invention, a web server provides a web page to a user terminal, receives a request message of a static resource used to configure the web page from the user terminal, A request analyzer for extracting information on the static resources and information on tenants included in the static resource; And a resource manager for receiving the static resource information and the tenant information from the request analysis unit and providing the static resource corresponding to the tenant to the user terminal using the information of the static resource and the information of the tenant, A static resource providing device is provided.

Wherein the resource management unit stores at least a part of the plurality of static resources for each tenant and corresponds to the tenant among the plurality of stored static resources using information of the static resource received from the request analysis unit and information of the tenant Can obtain the above-mentioned static resources.

The resource management unit caches location information of each stored static resource, and the static resource and the tenant information received from the request analysis unit, And acquire the static resource corresponding to the tenant stored using the location information of the static resource corresponding to the tenant.

The request analysis unit caches the history information about the requested static resource within a set time, and the resource management unit receives the history information about the static resource from the request analysis unit, and uses the history information about the static resource And obtain the static resource corresponding to the stored tenant.

The static resource may include at least one of a media file used to configure the web page, a Cascading Style Sheets (CSS) file, a script file, and a flash file.

According to another exemplary embodiment of the present invention, in the request analysis unit, the web server provides the web page to the user terminal, thereby receiving the request message of the static resource used to configure the web page from the user terminal ; Extracting the static resource information and the tenant information included in the request message of the static resource from the request analysis unit; Receiving information of the static resource and information of the tenant from the request analysis unit in a resource management unit; And providing the static resource corresponding to the tenant to the user terminal using the information of the static resource and the information of the tenant in the resource management unit.

Wherein the step of providing the static resource corresponding to the tenant to the user terminal comprises the steps of storing information of the static resource received from the request analysis unit, Acquire the static resource corresponding to the tenant among the plurality of stored static resources using the information of the tenant, and provide the static resource corresponding to the acquired tenant to the user terminal.

Wherein the resource management unit caches location information of each stored static resource and the step of providing the static resource corresponding to the tenant to the user terminal comprises storing information of the static resource received from the request analysis unit, Acquiring location information of the static resource corresponding to the tenant among the cached location information using the information and acquiring the static resource corresponding to the stored tenant using the location information of the static resource corresponding to the tenant And provide the static resource corresponding to the acquired tenant to the user terminal.

The request analysis unit may cache the history information about the requested static resource within the set time and receive the history information about the static resource from the request analysis unit in the resource management unit. Wherein the step of providing the static resource to the user terminal comprises the steps of: obtaining the static resource corresponding to the tenant stored using the history information on the static resource; To the terminal.

The static resource may include at least one of a media file used to configure the web page, a Cascading Style Sheets (CSS) file, a script file, and a flash file.

According to another exemplary embodiment of the present invention, in a request analysis unit, in conjunction with hardware, a request message of a static resource used to configure the web page from the user terminal as the web server provides the web page to the user terminal ; Extracting the static resource information and the tenant information included in the request message of the static resource from the request analysis unit; Receiving information of the static resource and information of the tenant from the request analysis unit in a resource management unit; And providing the static resource corresponding to the tenant to the user terminal using the information of the static resource and the information of the tenant, in the resource management unit, the computer program stored in the computer readable recording medium do.

According to embodiments of the present invention, static resources necessary for each tenant are variably provided using information of static resources and information of tenants, so that a customized service for various tenants can be easily provided with one source code or application can do. In other words, it is not necessary to implement the branching logic per tenant at the web page level unlike the conventional one.

In addition, according to the embodiment of the present invention, there is a separate node for providing static resources, thereby solving the problem of increased load of the web server due to an increase in tenants.

In addition, according to embodiments of the present invention, it is possible to quickly access stored static resources using location information or history information of cached static resources, thereby improving searching and providing speed of static resources.

1 is a block diagram for explaining a static resource providing apparatus according to an embodiment of the present invention;
2 is a block diagram showing a detailed configuration of a static resource provision apparatus according to an embodiment of the present invention.
3 is a block diagram showing a detailed configuration of a request analysis unit according to an embodiment of the present invention.
4 is a block diagram illustrating a detailed configuration of a resource management unit according to an embodiment of the present invention.
5 is a flowchart for explaining a static resource providing method according to an embodiment of the present invention.

Hereinafter, specific embodiments of the present invention will be described with reference to the drawings. The following detailed description is provided to provide a comprehensive understanding of the methods, apparatus, and / or systems described herein. However, this is merely an example and the present invention is not limited thereto.

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS Hereinafter, exemplary embodiments of the present invention will be described in detail with reference to the accompanying drawings. In the following description, well-known functions or constructions are not described in detail since they would obscure the invention in unnecessary detail. The following terms are defined in consideration of the functions of the present invention, and may be changed according to the intention or custom of the user, the operator, and the like. Therefore, the definition should be based on the contents throughout this specification. The terms used in the detailed description are intended only to describe embodiments of the invention and should in no way be limiting. Unless specifically stated otherwise, the singular form of a term includes plural forms of meaning. In this description, the expressions "comprising" or "comprising" are intended to indicate certain features, numbers, steps, operations, elements, parts or combinations thereof, Should not be construed to preclude the presence or possibility of other features, numbers, steps, operations, elements, portions or combinations thereof.

1 is a block diagram for explaining a static resource providing apparatus 100 according to an embodiment of the present invention. The static resource providing apparatus 100 according to an embodiment of the present invention variably provides static resources required for each tenant, and is a device for providing a static resource (resource) based on a SaaS (Software as a Service) Lt; / RTI > Here, a tenant is an organization composed of a plurality of users, for example, a corporation, a company, or a corporation.

Referring to FIG. 1, the first user terminal 10 can request a desired web page by accessing (logging in) a web page provided by the web server 30 according to the input of the first user, (Or a template of the web page) requested by the user. At this time, it is assumed that the first user is a member of tenant A. The first user terminal 10 may request the static resource providing apparatus 100 to receive the static resource of the web page provided from the web server 30 and the static resource providing apparatus 100 transmits the static resource to the first user terminal 100. [ (Not shown). Here, the static resource may be a media file, a Cascading Style Sheets (CSS) file, a script file, a flash file, or the like, which constitutes a web page. The media file may be, for example, a video file, an image file, etc., and the script file may be, for example, JavaScript. At this time, the static resource providing apparatus 100 can provide the corresponding static resource to the user terminal in consideration of the tenant of the user who requests the static resource. For example, the static resource providing device 100 may provide the first user terminal 10 with a file containing a static resource corresponding to the tenant A to which the first user belongs, for example, a logo image of the tenant A .

The second user terminal 20 can access a web page provided by the web server 30 according to an input of the second user to request a desired web page, (Or a template of a web page). At this time, it is assumed that the second user is a member of tenant B. The second user terminal 20 can request the static resource providing apparatus 100 to receive the static resource of the web page provided from the web server 30 and the static resource providing apparatus 100 transmits the static resource to the second user terminal 100. [ (20). As described above, the static resource providing apparatus 100 can provide the static resource to the user terminal in consideration of the tenant of the user who requests the static resource. For example, the static resource providing apparatus 100 may provide the second user terminal 20 with a file containing a static resource corresponding to the tenant B to which the second user belongs, for example, a logo image of the tenant B . That is, according to the embodiments of the present invention, even if the same tenant side requests the same static resource (for example, a file including a logo image), the static resources received by each tenant side may be different from each other. Accordingly, customized services for various tenants can be easily provided by a single source code or an application, and it is not necessary to implement branching logic for each tenant at a web page level unlike the prior art. In addition, according to the embodiment of the present invention, there is a separate node for providing static resources, thereby solving the problem of increased load of the web server 30 due to an increase in tenants.

Although FIG. 1 shows that the web server 30 is one for convenience of explanation, a plurality of web servers 30 may exist. For example, a plurality of web servers 30 may exist for each tenant, and users of the tenants may access the corresponding web server 30 through a different URL (Uniform Resource Locator). Hereinafter, a detailed configuration of the static resource providing apparatus 100 will be described with reference to FIGS.

2 is a block diagram showing a detailed configuration of a static resource providing apparatus 100 according to an embodiment of the present invention. 2, the static resource providing apparatus 100 according to an embodiment of the present invention includes a request analysis unit 102 and a resource management unit 104. [ Hereinafter, for convenience of explanation, it is assumed that the web server 30 receives a web page from the first user terminal 10 owned by a first user belonging to the tenant A and requests a static resource to the static resource providing apparatus 100 do.

The request analysis unit 102 receives the static resource request message from the user terminal 10 as the web server 30 provides the web page to the user terminal 10 and transmits the static resource included in the request message of the static resource And the tenant information to which the user belongs. As described above, the static resource may be a media file, a CSS file, a script file, a flash file, or the like, which constitutes a web page. Here, the static resource information is identification data that indicates which static resource the static resource requested by the user terminal 10 is, for example, the file name of the static resource, the file extension, the identifier of the web page in which the static resource is used . The information of the static resource may be changed according to the type of the web page provided from the web server 30 by the user terminal 10, the type of the tenant to which the user requesting the web page belongs, and the like. In addition, the information of the tenant may be identification data indicating the tenant of the tenant to which the user requesting the web page belongs, for example, the tenant's name, ID, URL, and the like. The tenant information may be extracted from the user's ID, for example, in the process of the user terminal 10 logging in to the web page provided by the web server 30. However, this is only an example, and the method of extracting information of tenants is not limited thereto. As described above, when a plurality of web servers 30 exist for each tenant, users of the tenants can access the corresponding web server 30 via different URLs, and the information of the tenants is extracted from the connection URL . The user terminal 10 may transmit the static resource information and the tenant information to the request analyzing unit 102 in a request message of a static resource. The request analysis unit 102 may transmit the static resource information and the tenant information to the resource management unit 104. The resource management unit 104 may correspond to the tenant using the static resource information and the tenant information It is possible to obtain a static resource.

In addition, the request analysis unit 102 can cache the history information for the requested static resource within the set time (for example, the last hour). The history information may include tenant information on the requested static resource and location information on which the static resource is stored. As described later, the resource management unit 104 can obtain the static resource corresponding to the tenant using the stored location information of each static resource. The request analysis unit 102 may transmit the history information about the cached static resource to the resource management unit 104. The resource management unit 104 may use the information of the tenant included in the history information and the location information of the static resource To obtain a static resource for the tenant.

The resource management unit 104 receives the static resource information and the tenant information from the request analysis unit 102, acquires the static resource corresponding to the tenant using the static resource information and the tenant information, And provides the static resource to the user terminal 10.

To this end, the resource management unit 104 may store at least a part of a plurality of static resources for each tenant. For example, a variable resource that needs to be separated by tenants among a plurality of static resources

Tenant A - Static Resource 1, Tenant A - Static Resource 2,

Tenant B - Static Resource 1, Tenant B - Static Resource 2

...

Or the like in a form of a resource management unit 104. [ The variable resource may be, for example, a tenant logo image file inserted variably (that is, different for each tenant) on a web page.

In addition, common resources that do not need to be distinguished by tenants include, for example,

Common - static resources 3

And may be stored in the resource management unit 104 in the form of The common resource may be, for example, an image file for a background screen that is commonly embedded in a web page (i.e., regardless of a tenant), a phrase on the web page, or a script file indicating the location of the image.

Also, the resource management unit 104 may cache location information of each stored static resource. The location information of the static resource is information indicating a storage location of the static resource stored in the resource management unit 104, and may be, for example, the name of a directory in which the static resource is stored, a URL, and the like. The resource management unit 104 obtains the location information of the static resource corresponding to the tenant among the cached location information using the static resource information and the tenant information received from the request analysis unit 102, The static resource corresponding to the tenant stored can be obtained by using the location information of the corresponding static resource. The location information may be obtained from the resource location information database 308 in the resource management unit 104 and cached.

Also, as described above, the request analyzer 102 can cache the history information about the requested static resource within the set time, and can transmit the history information about the cached static resource to the resource manager 104 . The history information may include tenant information on the requested static resource and location information on which the static resource is stored. Accordingly, the resource management unit 104 can immediately acquire the stored static resource using the history information received from the request analysis unit 102 without having to inquire the location information cached in the resource management unit 104. [

That is, according to the embodiments of the present invention, it is possible to quickly access stored static resources using the cached static resource location information or history information, thereby improving searching and providing speed of static resources.

In one embodiment, the request analysis unit 102 and the resource management unit 104 may be implemented on a computing device that includes one or more processors and a computer readable recording medium coupled to the processor. The computer readable recording medium may be internal or external to the processor, and may be coupled to the processor by any of a variety of well known means. A processor in the computing device may cause each computing device to operate in accordance with the exemplary embodiment described herein. For example, a processor may execute instructions stored on a computer-readable recording medium, and instructions stored on the computer readable medium may cause the computing device to perform operations according to exemplary embodiments described herein For example.

3 is a block diagram illustrating a detailed configuration of a request analysis unit 102 according to an embodiment of the present invention. 3, the request analysis unit 102 includes an analyzer 202 and a resource request history cache 204 according to an embodiment of the present invention.

The analyzer 202 receives the request message of the static resource from the user terminal 10 and extracts the information of the static resource included in the request message of the static resource and the information of the user's tenant. As described above, the static resources received by the respective tenants may be different even if they request the same static resources from different tenants. To this end, the analyzer 202 may analyze the request message of the static resource and extract the information of the requested static resource and the information of the tenant to which the user requesting the static resource belongs. In one example, the request message of the static resource received from the first user terminal 10 includes information on the logo.jpg file and information on the tenant A, and the static resource received from the second user terminal 10 The request message may include information on the logo.jpg file and information on tenant B. [ In this case, the analyzer 202 can identify not only the static resource information but also the tenant information included in the request message of each static resource, and transmit the information to the resource management unit 104. Accordingly, the resource management unit 104 can transmit the logo.jpg file corresponding to the tenant A and the logo.jpg file corresponding to the tenant B to the first user terminal 10 and the second user terminal 20, respectively . Here, the logo.jpg file corresponding to the tenant A and the logo.jpg file corresponding to the tenant B may be different from each other.

The resource request history cache 204 can cache history information for the requested static resources within a set time (e.g., the last hour). The resource request history cache 204 can receive the information about the requested static resource and the tenant within the set time from the analyzer 202 and can receive the location information in which the static resource is stored from the resource management unit 104 have. The analyzer 202 may transmit the history information on the static resource to the resource management unit 104 together with the static resource information and the tenant information. If the requested static resource is the same as the static resource included in the history information, the resource management unit 104 does not need to inquire the location information cached in the resource management unit 104 and uses the location information included in the history information So that stored static resources can be retrieved and acquired more quickly. If the requested static resource is not the same as the static resource included in the history information, the resource management unit 104 inquires the cached location information in the resource management unit 104 to acquire the location information of the corresponding static resource, And acquire a static resource corresponding to the tenant using the location information.

4 is a block diagram showing a detailed configuration of a resource management unit 104 according to an embodiment of the present invention. 4, the resource management unit 104 according to an embodiment of the present invention includes a resource relay unit 302, a static resource repository 304, a resource location information cache 306, and a resource location information database 308, .

The resource relayer 302 relays the static resource using the static resource information and the tenant information received from the request analysis unit 102. The resource repeater 302 can acquire a static resource corresponding to the tenant among the plurality of static resources stored in the static resource repository 304 using the static resource information and the tenant information received from the request analysis unit 102 have. At this time, the resource repeater 302 can obtain the static resource corresponding to the tenant by using the location information cached in the resource location information cache 306. [ The resource location information cache 306 caches location information of each static resource stored in the static resource repository 304. The resource relay 302 analyzes the static resource information and the tenant information received from the request analysis unit 102 And acquires location information of a static resource corresponding to the tenant among the location information cached in the resource location information cache 308 using the location information and stores the static information corresponding to the tenant stored in the static resource repository 304 Resources can be acquired.

The static resource repository 304 is a place where static resources are stored. As shown in FIG. 4, at least some of the plurality of static resources may be stored in the static resource repository 304 for each tenant. For example, a variable resource that needs to be separated by tenants among a plurality of static resources

Tenant A - Static Resource 1, Tenant A - Static Resource 2,

Tenant B - Static Resource 1, Tenant B - Static Resource 2

...

And the like in the form of a static resource record 304. [

In addition, common resources that do not need to be distinguished by tenants include, for example,

Common - static resources 3

May be stored in the static resource repository 304 in the form of < RTI ID = 0.0 > The common resource may be provided to the user terminal 10 together with a static resource corresponding to the tenant upon request of the static resource.

The resource location information cache 306 is a location where the location information of each static resource stored in the static resource repository 304 is cached. The location information of the static resource is information indicating a storage location of the static resource stored in the static resource repository 304, and may be, for example, the name of a directory in which the static resource is stored, a URL, and the like. The location information may be obtained from the resource location information database 308 and cached.

The resource location information database 308 is a location where location information of each static resource stored in the static resource repository 304 is stored. As an example, all of the location information stored in the resource location information database 308 when the resource location information cache 306 is activated may be cached in the resource location information cache 306, The location information of the static resource can be obtained by accessing the resource location information cache 306 rather than the location information cache 308. Thus, searching and providing speed of static resources can be improved. As another example, some of the location information stored in the resource location information database 308 may be cached in the resource location information cache 306. [ At this time, the location information cached in the resource location information cache 306 may include, for example, location information of the retrieved static resource more than the set number of times (for example, five times), static resource having relatively high importance And the like.

5 is a flowchart illustrating a static resource providing method according to an embodiment of the present invention. The method shown in Fig. 5 can be performed, for example, by the static resource providing apparatus 100 described above. In the illustrated flow chart, the method is described as being divided into a plurality of steps, but at least some of the steps may be performed in reverse order, combined with other steps, performed together, omitted, divided into detailed steps, One or more steps may be added and performed.

First, the request analysis unit 102 receives a static resource request message used to configure a web page from the user terminal 10 (S502). As described above, the user terminal 10 accesses (logs in) a web page provided by the web server 30, requests a desired web page, receives a requested web page from the web server 30, The request analysis unit 102 may request the static resource of the request analysis unit 102. [

Next, the request analysis unit 102 extracts the information of the static resources and the information of the tenants included in the request message of the static resource (S504). The information of the static resource may be, for example, a file name of a static resource, a file extension, an identifier of a web page in which a static resource is used, and the like. Also, the information of the tenant may be, for example, the tenant's name, ID, URL, and the like.

Next, the request analysis unit 102 confirms the latest history information about the requested static resource (S506). As described above, the request analysis unit 102 may cache the history information about the requested static resource within a predetermined time (for example, the last one hour), and the resource management unit 104 may use the history information And obtain a static resource for the tenant. The history information may include tenant information on the requested static resource and location information on which the static resource is stored.

Next, the request analysis unit 102 transmits the static resource information, the tenant information, and the history information included in the static resource request message to the resource management unit 104 (S508).

Next, the resource management unit 104 determines whether the requested static resource is a newly requested resource (S510).

If it is determined in step S510 that the requested static resource is a newly requested resource, the resource management unit 104 uses the static resource information and the tenant information received from the request analysis unit 102 to generate a corresponding static resource And acquires the stored location information (S512). As described above, the resource manager 104 caches location information of a static resource (that is, a variable resource) or a common resource for each tenant stored therein, and stores location information of a static resource corresponding to the tenant among the plurality of cached location information Can be obtained.

Next, the resource management unit 104 acquires a static resource corresponding to the tenant among the stored plurality of static resources using the acquired location information (S514).

Finally, the resource management unit 104 transmits the static resource obtained in the step S514 to the user terminal 10 as a response to the requested static resource (S516).

On the other hand, if it is determined in step S510 that the requested static resource is not a newly requested resource, the resource management unit 104 acquires the static resource corresponding to the tenant using the history information, To the terminal 10 (S516). As described above, the location information of the requested static resource is included in the history information. Therefore, the resource management unit 104 can directly obtain the requested static resource using the history information without going through steps S512 and S514 have.

On the other hand, an embodiment of the present invention may include a program for performing the methods described herein on a computer, and a computer-readable recording medium including the program. The computer-readable recording medium may include a program command, a local data file, a local data structure, or the like, alone or in combination. The media may be those specially designed and constructed for the present invention, or may be those that are commonly used in the field of computer software. Examples of computer-readable media include magnetic media such as hard disks, floppy disks and magnetic tape, optical recording media such as CD-ROMs and DVDs, and specifically configured to store and execute program instructions such as ROM, RAM, flash memory, Hardware devices. Examples of such programs may include machine language code such as those produced by a compiler, as well as high-level language code that may be executed by a computer using an interpreter or the like.

While the present invention has been particularly shown and described with reference to exemplary embodiments thereof, it is to be understood that the invention is not limited to the disclosed embodiments, but, on the contrary, I will understand. Therefore, the scope of the present invention should not be limited to the above-described embodiments, but should be determined by equivalents to the appended claims, as well as the appended claims.

10: first user terminal
20: second user terminal
30: Web server
100: Static resource provisioning device
102:
104:
202: Analyzer
204: Resource request history cache
302: Resource Repeater
304: Static Resource Store
306: Resource location information cache
308: Resource location information database

Claims (11)

The web server receives a request message of a static resource used to configure the web page from the user terminal in response to providing a web page to a user terminal, and receives information of the static resource included in the request message of the static resource, A request analyzing unit for extracting information of a user; And
A resource manager for receiving the static resource information and the tenant information from the request analyzer and providing the static resource corresponding to the tenant to the user terminal using the static resource information and the tenant information, A static resource provisioning device.
The method according to claim 1,
Wherein the resource management unit stores at least a part of a plurality of static resources for each tenant,
And obtains the static resource corresponding to the tenant among the plurality of static resources stored using the static resource information and the tenant information received from the request analysis unit.
The method of claim 2,
The resource management unit caches location information of each stored static resource,
Acquiring location information of the static resource corresponding to the tenant among the cached location information using the information of the static resource received from the request analysis unit and the information of the tenant, And obtains the static resource corresponding to the tenant stored using the location information.
The method of claim 3,
The request analyzer caches the history information of the requested static resource within a set time,
Wherein the resource management unit receives the history information on the static resource from the request analysis unit and acquires the static resource corresponding to the stored tenant using the history information on the static resource.
The method according to claim 1,
Wherein the static resource includes at least one of a media file used to configure the web page, a Cascading Style Sheets (CSS) file, a script file, and a flash file.
Receiving a static resource request message used to configure the web page from the user terminal in response to the web server providing the web page to the user terminal;
Extracting the static resource information and the tenant information included in the request message of the static resource from the request analysis unit;
Receiving information of the static resource and information of the tenant from the request analysis unit in a resource management unit; And
And providing the static resource corresponding to the tenant to the user terminal using the information of the static resource and the information of the tenant in the resource management unit.
The method of claim 6,
Wherein the resource management unit stores at least a part of a plurality of static resources for each tenant,
Wherein the step of providing the static resource corresponding to the tenant to the user terminal comprises the steps of storing the static resource information and the tenant information received from the request analysis unit, Acquiring the static resources, and providing the static resources corresponding to the acquired tenants to the user terminal.
The method of claim 7,
The resource management unit caches location information of each stored static resource,
Wherein the step of providing the static resources corresponding to the tenant to the user terminal comprises the steps of: receiving information on the static resource received from the request analysis unit and information on the tenant, Acquiring location information of the static resource, acquiring the static resource corresponding to the stored tenant using the location information of the static resource corresponding to the tenant, and transmitting the static resource corresponding to the acquired tenant to the user terminal To a static resource providing method.
The method of claim 8,
The request analyzer caches the history information of the requested static resource within a set time,
Further comprising the step of, in the resource management unit, receiving history information on the static resource from the request analysis unit,
Wherein the step of providing the static resource corresponding to the tenant to the user terminal comprises the steps of obtaining the static resource corresponding to the stored tenant using the history information on the static resource, And provides the resource to the user terminal.
The method of claim 6,
Wherein the static resource includes at least one of a media file used to configure the web page, a Cascading Style Sheets (CSS) file, a script file, and a flash file.
Combined with hardware
Receiving a static resource request message used to configure the web page from the user terminal in response to the web server providing the web page to the user terminal;
Extracting the static resource information and the tenant information included in the request message of the static resource from the request analysis unit;
Receiving information of the static resource and information of the tenant from the request analysis unit in a resource management unit; And
Providing the static resource corresponding to the tenant to the user terminal using the information of the static resource and the information of the tenant in the resource management unit
The computer program being stored on a computer readable recording medium.
KR1020150130293A 2015-09-15 2015-09-15 Apparatus and method for providing static resources for multi-tenant KR20170032669A (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
KR1020150130293A KR20170032669A (en) 2015-09-15 2015-09-15 Apparatus and method for providing static resources for multi-tenant

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
KR1020150130293A KR20170032669A (en) 2015-09-15 2015-09-15 Apparatus and method for providing static resources for multi-tenant

Publications (1)

Publication Number Publication Date
KR20170032669A true KR20170032669A (en) 2017-03-23

Family

ID=58496023

Family Applications (1)

Application Number Title Priority Date Filing Date
KR1020150130293A KR20170032669A (en) 2015-09-15 2015-09-15 Apparatus and method for providing static resources for multi-tenant

Country Status (1)

Country Link
KR (1) KR20170032669A (en)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113760351A (en) * 2021-03-24 2021-12-07 北京京东拓先科技有限公司 Project uploading method and device, electronic equipment and computer readable medium

Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR20120044516A (en) 2010-10-28 2012-05-08 한국전자통신연구원 Configuration and management of web pages for multi-tenant

Patent Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR20120044516A (en) 2010-10-28 2012-05-08 한국전자통신연구원 Configuration and management of web pages for multi-tenant

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113760351A (en) * 2021-03-24 2021-12-07 北京京东拓先科技有限公司 Project uploading method and device, electronic equipment and computer readable medium

Similar Documents

Publication Publication Date Title
US9171092B2 (en) Personal assistant context building
US10848542B2 (en) Systems and methods for web API communication
US8935798B1 (en) Automatically enabling private browsing of a web page, and applications thereof
US20190190977A1 (en) System and method of automatic generation and insertion of analytic tracking codes
US10776444B1 (en) Methods and systems for universal deep linking across web and mobile applications
US7987243B2 (en) Method for media discovery
US11106754B1 (en) Methods and systems for hyperlinking user-specific content on a website or mobile applications
US10922372B1 (en) Methods and systems for generating custom content using universal deep linking across web and mobile applications
WO2015139539A1 (en) Video information push method and device
US20160042087A1 (en) Method, System And Front -End Device For Posting User Generated Content
AU2017265064A1 (en) Access to data on a remote device
KR101509226B1 (en) System and method for providing mobile url in mobile search environment
KR101659147B1 (en) Information processing apparatus, and control method therefor
US20130019017A1 (en) Client bundle resource creation
KR20170032669A (en) Apparatus and method for providing static resources for multi-tenant
CN113590985B (en) Page jump configuration method and device, electronic equipment and computer readable medium
US10417296B1 (en) Intelligent bookmarking with URL modification
US10599740B1 (en) Program code streaming
CN104035970B (en) A kind of method and apparatus scanned in a browser
US10628220B2 (en) Information processing system, information processing method, and non-transitory computer-readable storage medium for storing program
US9215150B2 (en) Feature set negotiation framework
CN110209959B (en) Information processing method and device
KR20160132854A (en) Asset collection service through capture of content
US10079739B2 (en) Computer-implemented method for handling log file
US20130290830A1 (en) System and method for managing a viewstate of a web application