JP5097090B2 - Content distribution device - Google Patents

Description

  The present invention relates to a data processing technique, and more particularly to a technique for distributing web page content.

Currently, many companies send information by providing web pages to customers. Examples of content included in the web page (hereinafter also referred to as “web content” as appropriate) include introduction information on new products and services, and information on sales offices. Individual web content is typically created by business personnel in various departments of the company.
JP 2002-189677 A

  In general, business staff who create web content are good at business knowledge, but are familiar with the technical content required to provide web content to customers, such as the configuration of the web system. Often not. One web content created by a person in charge of business may be displayed on various web pages, and even one web content should be provided to many web servers. Therefore, when the business staff is responsible for providing web content to the web server, the burden on the business staff may be increased.

  The present invention has been made in view of these problems, and a main object thereof is to provide a technology that supports appropriate distribution of web content to a web server.

  In order to solve the above problems, a content distribution apparatus according to an aspect of the present invention includes a server information storage unit that stores a correspondence relationship between a web page and a web server that provides the web page, and a web page to be posted. In order to prevent the content creator from having to be aware of the registration acceptance unit that accepts registration requests for new content from the content creator in a unified manner and the web server where the new content should actually be placed. A distribution unit that identifies a web server that provides the web page specified in the registration request and transmits new content to the identified web server asynchronously with the registration request.

  It should be noted that any combination of the above-described constituent elements and a representation of the present invention converted between an apparatus, a method, a system, a program, a recording medium storing the program, and the like are also effective as an aspect of the present invention.

  According to the present invention, it is possible to support appropriate distribution of web content to a web server.

The outline of the embodiment will be described before the configuration thereof is described.
Providing web pages is now indispensable as a means of transmitting information from companies. Since actively transmitting information to customers affects the success or failure of business, it is desirable that fresh web content is always posted on a company web page. For this purpose, a system is required that can easily provide the created web content to the web server even for a business person who does not necessarily have high computer literacy (hereinafter referred to as “content creator” as appropriate). .

  The content distribution system proposed in the embodiment centrally executes distribution of web content and virtualizes physical information such as the location of the web server. This eliminates the need for the content creator to be aware of the physical configuration of the web system. In this content distribution system, the concept of a content group indicating a partial area of a web page is introduced, and web content is managed in units of content groups. The content creator needs to be responsible for the content group, not the entire web page, and the scope of responsibility is limited. Thereby, the content creator can easily provide the web content. The configuration will be described below.

  FIG. 1 shows a configuration of a content distribution system according to an embodiment of the present invention. The content distribution system 1000 includes a first creator terminal 100a, a second creator terminal 100b, a third creator terminal 100c, which are collectively referred to as the creator terminal 100, a content distribution apparatus 200, and a distribution data storage apparatus 300. And a first web server 400a, a second web server 400b, and a third web server 400c, which are collectively referred to as the web server 400. Each apparatus is appropriately connected by a known communication means such as a LAN, WAN, or the Internet.

  The creator terminal 100 is a general PC terminal and is operated by a content creator. The creator terminal 100 transmits data (hereinafter referred to as “registration request data” as appropriate) to instruct the web server to place the web content created by the content creator on the web server.

  The content distribution apparatus 200 receives registration request data from the creator terminal 100 in a centralized manner. Then, distribution data obtained by appropriately collecting the web contents included in each registration request data is distributed to an appropriate web server 400 via the distribution data storage device 300. Details of the content distribution apparatus 200 will be described later.

  The distribution data storage device 300 is a NAS (Network Attached Storage) device, and in each storage area associated with each of the first web server 400a, the second web server 400b, and the third web server 400c, The distribution data to be acquired by the web server 400 is stored. This storage area may be implemented as a FIFO (First-In First-Out) queue.

  The web server 400 provides web content in response to a request from a customer terminal (not shown). The “web server” in the present specification broadly means a device that provides at least a part of web contents among various web contents displayed on a web page. That is, when the term “web server” is simply used, it includes not only a computer in which web server software such as Apache is installed, but also an application server in which a servlet engine is installed. Also included is a content delivery server that typically holds an image file or the like and provides a content delivery service that is provided upon request.

  The web server 400 acquires distribution data from the distribution data storage device 300 at a predetermined timing such as a specific date and time. According to the distribution data, the web server 400 starts providing web content by storing the web content in a predetermined storage area, or stops providing web content by discarding the web content.

  FIG. 2 is a block diagram showing a functional configuration of the content distribution apparatus 200 of FIG. The content distribution device 200 includes a content storage unit 10, a server information storage unit 12, a registration reception unit 14, a distribution file generation unit 16, a stop file generation unit 18, and a distribution unit 20.

  Each block shown in the block diagram of the present specification can be realized in terms of hardware by an element such as a CPU of a computer or a mechanical device, and in terms of software, it can be realized by a computer program or the like. The functional block realized by those cooperation is drawn. Therefore, those skilled in the art will understand that these functional blocks can be realized in various forms by a combination of hardware and software.

  The content storage unit 10 is a storage area for storing registration request data transmitted from the creator terminal 100. FIG. 3 shows the structure of registration request data. In the “web page ID” column, identification information of a web page on which web content is to be displayed, for example, a URL (Uniform Resource Locator) is set.

  The “content group ID” column is an area that constitutes a part of the web page, and content group identification information for displaying one or more web contents in the area is set. Typically, this content group is an area including a plurality of web contents having the same theme. For example, it may be a category-specific display area such as “notification” or “product information” that categorizes web content displayed simultaneously on one web page. Further, for example, each of a plurality of frames that are apparently displayed on one web page may be a content group.

  In the “content name” column, the file name of the web content is set. In the “content data” column, text data and binary data of web contents are set. In the “posting start date and time” column, the date and time when the web content should be started to be posted on the web page is set. In the “posting stop date / time” column, the date and time at which the posting of the web content on the web page should be stopped is set.

  In the “arrangement order” column, the order in which the web contents are arranged on the web server is set for the web contents in which different content groups are set and the same insertion start date and time is set. As an example, consider a case where the first web content refers to the content of the second web content in which a different content group is set. Specifically, this is a case where a first JSP (Java (registered trademark) Server Pages) file includes a second JSP file. In this case, since the second web content needs to be arranged on the web server before the first web content, the arrangement order ahead of the first web content is set for the second web content. . Returning to FIG.

  The server information storage unit 12 is a storage area for storing a correspondence relationship between a plurality of web pages and a plurality of web servers that provide each of the plurality of web pages. FIG. 4 shows the structure of stored data in the server information storage unit 12.

  The web page with the web page ID “w001” has two content groups with content group IDs “c001” and “c002”. The content group with the content group ID “c001” has different web servers to be arranged depending on the file extension of the web content, that is, the file type of the web content. In FIG. 4, a first web server that is a content delivery server is set for the MPEG file, a second web server that is a narrow web server is set for the HTML file, and a third web server that is an application server is set for the JSP file. . Note that the content group with the content group ID “c002” is not distinguished for each file extension, and the second web server is set in common.

  Further, the web page with the web page ID “w002” is not distinguished for each content group ID, and the fourth web server and the fifth web server are set in common. When a plurality of web servers provide the same web page, typically, when load balancing of websites is performed by a plurality of web servers, a plurality of web pages are assigned to one “web page ID”. Web server is set up. Returning to FIG.

  The registration receiving unit 14 centrally receives registration request data transmitted from each of the first creator terminal 100a, the second creator terminal 100b, and the third creator terminal 100c and stores them in the content storage unit 10. Remember. When a plurality of web page IDs are specified in the registration request data received from the creator terminal 100, the registration receiving unit 14 duplicates the registration request data for each web page ID and stores it in the content storage unit 10. Let

  When the registration request data is stored in the creator terminal 100, the registration receiving unit 14 transmits data indicating that the registration request data has been received to the creator terminal 100 of the transmission source.

  The distribution file generation unit 16 generates a distribution file for distributing the web content on the web server 400 as distribution data in order to place the web content on the web page. In this distribution file, web contents are collected for each web page ID and content group ID specified in the registration request data. Further, the distribution file generation unit 16 generates a tag file that retains the attribute of the distribution file and associates it with the distribution file. Hereinafter, specific processing contents of the distribution file generation unit 16 will be described.

  First, when the distribution file generation unit 16 detects that the current date and time is the date and time when the distribution file should be generated, the distribution file generation unit 16 specifies the posting start date and time of the registration request data to be aggregated based on the current time. Then, the registration request data in which the posting start date / time is set is acquired from the content storage unit 10. For example, when the current date and time is January 1st 10:35, registration request data may be acquired in which January 1 10:40, which is five minutes later, is set as the publication start date and time.

  Next, the distribution file generation unit 16 specifies one or more registration request data (hereinafter referred to as “distribution target data” as appropriate) having the same web page ID and content group ID among the acquired registration request data. That is, one or more distribution target data is specified for each combination of web page ID and content ID.

  The distribution file generation unit 16 refers to the server information storage unit 12 and further associates a file extension when the combination of the web page ID and the content group ID is associated with a different web server ID for each file extension. The distribution target data is classified for each. The distribution file generation unit 16 generates a distribution file by compressing the content data of the distribution target data. In the server information storage unit 12, when a combination of a web page ID and a content group ID is associated with a plurality of web server IDs, distribution to a plurality of web servers specified by each web server ID is performed. In order to replicate the distribution file.

  Next, the distribution file generation unit 16 generates a tag file for each generated distribution file and associates it with the distribution file. FIG. 5 shows the data structure of the tag file associated with the distribution file. The distribution file generation unit 16 sets the web server ID, content group ID, and publication start date / time specified when generating the distribution file as tag file data to be associated with the distribution file.

  Further, the distribution file generation unit 16 further sets the arrangement order for each tag file for the distribution files having the same web server ID and posting start date and time. When setting the arrangement order, the distribution file generation unit 16 (1) determines the arrangement order in each tag file according to the arrangement order set for each distribution target data. When a plurality of distribution target data exist in one distribution file, the largest arrangement order among the arrangement orders set for each distribution target data may be set in the tag file. As a modification, (2) it may be determined according to an arrangement order set in advance for each content group, or (3) it may be determined according to the order received by the registration receiving unit 14. Furthermore, the arrangement order may be determined by combining these determination methods with the priority of the above (1)> (2)> (3). Returning to FIG.

  The stop file generation unit 18 generates a stop file for distributing the web content on the web page to the web server 400 as distribution data. In this stop file, web content identification information is collected for each web page ID and content group ID specified in the registration request data. Further, the stop file generation unit 18 generates a tag file that retains the attribute of the stop file and associates it with the distribution file. Hereinafter, specific processing contents of the stop file generation unit 18 will be described.

  First, when the stop file generation unit 18 detects that the current date and time is the date and time when the stop file should be generated, the stop file generation unit 18 specifies the publication stop date and time of registration request data to be aggregated based on the current time. Then, the registration request data in which the posting stop date / time is set is acquired from the content storage unit 10. For example, when the current date and time is January 1 at 10:35, registration request data may be acquired in which January 1 10:40, which is five minutes later, is set as the posting stop date and time.

  Next, the stop file generation unit 18 specifies one or more registration request data (hereinafter, referred to as “stop target data” as appropriate) having a common web page ID and content group ID among the acquired registration request data. That is, one or more stop target data is specified for each combination of the web page ID and the content ID.

  The stop file generation unit 18 refers to the server information storage unit 12 and further expands the file when the combination of the web page ID and the content group ID is associated with a different web server ID for each file extension. Classify the data to be stopped for each child. The stop file generation unit 18 generates a stop file in which the content name of the stop target data is set as data. In the server information storage unit 12, when a combination of a web page ID and a content group ID is associated with a plurality of web server IDs, distribution to a plurality of web servers specified by each web server ID is performed. In order to replicate the stop file.

  Next, the stop file generation unit 18 generates a tag file for each generated stop file and associates it with the stop file. FIG. 6 shows the data structure of the tag file associated with the stop file. The stop file generation unit 18 sets the web server ID, content group ID, and publication stop date / time specified when generating the stop file as tag file data to be associated with the stop file.

  Moreover, the stop file production | generation part 18 sets further the discard order with respect to each tag file about the stop file with which web server ID and insertion stop date are common. When setting the discard order, the stop file generation unit 18 determines (1) the discard order in each tag file according to the arrangement order set for each stop target data. If it is assumed that there will be no problem in the discarding process if discarded in the reverse order of the arrangement order, the reverse order of the arrangement order may be determined as the discarding order. As a modification, (2) it may be determined according to the discard order set in advance for each content group, or (3) it may be determined according to the order received by the registration receiving unit 14. Similarly to (1), in the case of (3), the reverse order of the acceptance order may be determined as the discard order. Furthermore, the discarding order may be determined by combining these determination methods with the priority (1)> (2)> (3). Returning to FIG.

  The distribution unit 20 transmits the distribution file and tag file generated by the distribution file generation unit 16 and the stop file and tag file generated by the stop file generation unit 18 to the distribution data storage device 300. Specifically, the storage area of the distribution data storage device 300 associated with the web server ID is specified with reference to the web server ID set in the tag file. Then, the tag file and the distribution file or stop file associated with the tag file are stored in the specified storage area.

The operation of the above configuration will be described below.
FIG. 7 is a flowchart showing operations of the creator terminal 100 and the content distribution apparatus 200. The creator terminal 100 transmits registration request data for the web content created by the content creator to the content distribution apparatus 200 (S10). The registration receiving unit 14 of the content distribution apparatus 200 receives registration request data from the creator terminal 100 (S12). The registration receiving unit 14 stores the registration request data in the content storage unit 10 and notifies the creator terminal 100 of the completion of reception of the registration request data (S14). The creator terminal 100 displays the completion of acceptance of the registration request data on the screen (S16).

  FIG. 8 is a flowchart showing the operation of the content distribution apparatus 200. When the distribution file generation unit 16 detects a distribution file generation trigger, for example, that the current date and time has become a predetermined date and time (Y in S20), the content file generation unit 16 refers to the content storage unit 10 and the server information storage unit 12 and the content data A compressed distribution file is generated (S22). Then, a tag file indicating the attribute of the distribution file is generated and associated with the distribution file (S24). The distribution unit 20 transmits the distribution file and the tag file associated with the distribution file to the distribution data storage device 300 for storage (S26). When the distribution file generation trigger is not detected (N in S20), S22 to S26 are skipped.

  When the stop file generation unit 18 detects a stop file generation trigger, for example, that the current date and time has become a predetermined date and time (Y in S28), the stop file generation unit 18 refers to the content storage unit 10 and the server information storage unit 12 to generate a stop file. Generate (S30). Then, a tag file indicating the attribute of the stop file is generated and associated with the stop file (S32). The distribution unit 20 transmits and stores the stop file and the tag file associated with the stop file to the distribution data storage device 300 (S34). When the stop file generation trigger is not detected (N in S28), the process returns to S20. In FIG. 6, the processing from S20 to S26 and the processing from S28 to S34 are shown in series, but they may be executed in parallel.

  FIG. 9 is a flowchart showing the operation of the web server 400. The web server 400 waits until it detects a delivery data acquisition trigger, for example, that the current date and time has become a predetermined date and time (N in S40). When detecting the distribution data acquisition trigger (Y in S40), the web server 400 accesses the distribution data storage device 300 and acquires the distribution data stored in the storage area for the server itself (S42). When the acquired distribution data is a distribution file and its tag file (Y in S44), the web server 400 waits until the publication start date and time specified in the tag file (N in S46). When the current date / time becomes the publication start date / time (Y in S46), the web server 400 acquires the web content by decompressing the compressed distribution file, and stores the content group specified by the content ID of the tag file. The web content is arranged in the area (S48). Thereby, the posting of the web content on the web page is started.

  When the acquired distribution data is the stop file and its tag file (N in S44), the web server 400 waits until the publication stop date and time specified in the tag file (N in S50). When the current date / time becomes the publication stop date / time (Y in S50), the web server 400 refers to the stop file, identifies the web content name to be discarded, and the content group designated by the content ID of the tag file is arranged. The web content is deleted from the storage area (S52). Thereby, the posting of the web content on the web page is stopped.

  According to the content distribution system 1000 of the present embodiment, even a content creator who does not have high computer literacy can easily distribute the created web content to the web server.

  Specifically, the content distribution apparatus 200 conceals the system configuration such as the position of the web server from the content creator, and accepts the web content centrally regardless of the distribution destination. In addition, the web content is appropriately copied according to the number of distribution destinations. Thereby, the content creator can easily distribute the web content without being aware of the actual distribution time and distribution means when the web content is distributed to the web server. In addition, since the content registration request by the content creator and the actual content distribution are executed asynchronously, the content creator only needs to register the content in the content distribution apparatus 200, and the burden is reduced. .

  Further, according to the content distribution system 1000, the web content update in the web server 400 is executed in units of content groups. When the entire web page is an update unit, duplication of file names among a plurality of web contents is likely to occur, and the burden on the content creator other than the original business of creating web contents increases. On the other hand, according to the present embodiment, the content creator only needs to be responsible for the content group in which the created web content is displayed, the range of responsibility is limited, and the burden is reduced.

  For the same reason, the system administrator of the content distribution system 1000 can easily divide the system management unit to facilitate system management. In addition, since the content group is an area where web content having the same theme is displayed, the content group can be reused in units of content groups, in other words, the same content group can be easily used in a plurality of web pages. As described above, even if the content group is used in a plurality of web pages, the content data is duplicated in the content distribution device 200 and does not increase the burden on the content creator.

  Furthermore, according to the content distribution system 1000, web content is arranged in the web server and discarded according to the designation of the publication start date / time and the publication stop date / time by the content creator. The content creator can set the posting start date / time and the posting stop date / time as parameters according to business circumstances without being aware of the system, and the burden is reduced. Moreover, not only the date and time when the web content is started to be published, but also the date and time when the content is stopped can be specified, so that the posting of the web content that has become meaningless in business and should be disabled can be appropriately stopped. It is particularly suitable for web contents for notifying a limited time campaign.

  Furthermore, according to the content distribution system 1000, the arrangement order and the discard order are set in the tag file. Thus, when web contents are arranged and discarded in the web server, the web contents are arranged and discarded in the order corresponding to the dependency relationship of the web contents across the content groups. Furthermore, an appropriate distribution destination is determined according to the file type of the web content without making the content creator aware of it. This can further reduce the burden on the content creator.

  Furthermore, according to the content distribution system 1000, the content distribution device 200 and the web server 400 asynchronously transmit and receive web content via the distribution data storage device 300, so that one failure or the like affects the other. Can be prevented.

  The present invention has been described based on the embodiments. This embodiment is an exemplification, and it will be understood by those skilled in the art that various modifications can be made to combinations of the respective constituent elements and processing processes, and such modifications are also within the scope of the present invention. is there.

  As a modification, the distribution file generation unit 16 may encrypt the distribution file according to a known encryption algorithm. The distribution file generation unit 16 further sets an encryption flag indicating the presence / absence of encryption as tag file data associated with the distribution file. When the web server 400 detects the encryption of the distribution file with reference to the encryption flag of the tag file, the web server 400 decrypts the distribution file according to a known decryption algorithm to obtain the web content. According to this modification, security in the distribution of web content can be improved. Of course, the stop file generation unit 18 may encrypt the stop file.

  As another modification, the distribution file generation unit 16 may further set the file size of the distribution file as tag file data associated with the distribution file. When the web server 400 acquires the distribution file and the tag file, the web server 400 compares the file size recorded in the tag file with the file size of the distribution file. When the two file sizes do not match, the web server 400 acquires the distribution file from the web server 400 again. As a result, it is possible to detect information loss at the time of distribution file acquisition and improve the reliability of distribution file acquisition. Of course, the stop file generation unit 18 may use tag file data that associates the file size of the stop file with the stop file.

  As yet another modification, the distribution file generation unit 16 may calculate a hash value of the distribution file according to a known hash algorithm, and further set the hash value as tag file data associated with the distribution file. When the web server 400 acquires the distribution file and the tag file, the web server 400 calculates a hash value of the distribution file and compares it with the hash value recorded in the tag file. When the two hash values do not match, the web server 400 discards the acquired distribution file. As a result, it is possible to detect information loss of the distribution file and the possibility of falsification of the distribution file, thereby improving the certainty of obtaining the distribution file and improving security. The same applies to the stop file.

  As yet another modification, only the web page ID, the content group ID, the content name, and the publication stop date / time may be set in the registration request data. This registration request data is typically transmitted from the creator terminal 100 to the content distribution device 200 when the web content already posted on the web page is to be deleted. In the content distribution device 200, the stop file is generated in the stop file generation unit 18 without the distribution file generation unit 16 generating the distribution file. In this modified example, since the specified quantity was reached during the campaign period of limited quantity, the web content was stopped from being posted at an arbitrary timing according to business circumstances, such as deleting the web content that announces the campaign. Particularly suitable for power cases.

  In the embodiment, the distribution data is distributed from the content distribution device 200 to the web server 400 via the distribution data storage device 300. However, the distribution data is transmitted from the content distribution device 200 to the web server 400. It may be sent directly. In addition, the communication protocol at that time is not particularly limited, and any communication protocol such as HTTP, FTP, NFS, etc. may be adopted. Further, as the web server ID of the server information storage unit 12, the IP address of each of the web servers 400 and the communication protocol for access may be recorded, and distribution data may be transmitted using those information.

  Any combination of the above-described embodiments and modifications is also useful as an embodiment of the present invention. The new embodiment generated by the combination has the effects of the combined embodiment and the modified examples.

  It should also be understood by those skilled in the art that the functions to be fulfilled by the constituent elements recited in the claims are realized by the individual constituent elements shown in the embodiments and the modified examples or by their linkage.

It is a figure which shows the structure of the content delivery system which is embodiment of this invention. It is a block diagram which shows the function structure of the content delivery apparatus of FIG. It is a figure which shows the structure of registration request data. It is a figure which shows the structure of the memory | storage data in a server information storage part. It is a figure which shows the data structure of the tag file matched with a distribution file. It is a figure which shows the data structure of the tag file matched with a stop file. It is a flowchart which shows operation | movement of a creator terminal and a content delivery apparatus. It is a flowchart which shows operation | movement of a content delivery apparatus. It is a flowchart which shows operation | movement of a web server.

Explanation of symbols

  DESCRIPTION OF SYMBOLS 10 Content memory | storage part, 12 Server information memory | storage part, 14 Registration reception part, 16 Distribution file generation part, 18 Stop file generation part, 20 Distribution part, 100 Creator terminal, 200 Content distribution apparatus, 300 Distribution data storage apparatus, 400 Web Server, 1000 content distribution system.

Claims (6)

A server information storage unit that stores a correspondence between a web page and a web server that provides the web page;
A web page on which new content is to be posted, a content group to which new content is to be posted, among the content groups constituting each of a plurality of partial areas forming the web page, and new content on the web page A registration accepting unit that centrally accepts registration requests for new content from the content creator,
(A) In order to start the posting of a plurality of new contents with the same posting start date / time at the same time on the web server, the distribution is performed by consolidating the new contents for each content group specified in the registration request and each posting start date / time. Means for generating a file and associating the distribution file with data indicating the date of start of publication, and (B) so that the content creator does not need to be aware of the web server on which the new content is actually placed. Means for identifying a web server on which new content included in the distribution file is to be placed with reference to the correspondence relationship, and associating data indicating the identified web server with each distribution file; and (C) the same publication start date and time For multiple distribution files associated with data indicating Tsu identify layout order to define the order in which to place the web server, and the distribution file generating unit comprising means for associating data indicating the respective arrangement order in each distribution file, and
Asynchronously with the registration request, a distribution unit that identifies a web server to be arranged with reference to data associated with the distribution file, and transmits the distribution file to the identified web server;
A content distribution apparatus comprising: A stop file generator,
The registration accepting unit accepts a registration request in which a new content posting stop date and time on a web page is further specified,
In order to stop the posting of a plurality of new contents with the same posting stop date and time at the same time on the web server, the stop file generation unit creates a new content for each content group and posting stop date and time specified in the registration request. Generate a stop list that aggregates the identification information of and associate data indicating the stop date and time with the stop list,
The content distribution apparatus according to claim 1, wherein the distribution unit further transmits a stop list to the identified web server. The stop file generation unit specifies a discard order that defines an order in which content to be stopped is discarded in a web server for a plurality of stop lists associated with data indicating the same stop date and time. The content distribution apparatus according to claim 2, wherein data indicating the discard order is further associated with each stop list. The content distribution apparatus according to claim 3, wherein the stop file generation unit specifies the reverse order of the arrangement order as the discard order. The distribution file generation unit identifies the file type of the new content, generates a distribution file in which the new content is aggregated for each content group, the posting start date and time and the file type specified in the registration request,
The distribution unit, each of the distribution file generated in accordance with each file type, claim 1, characterized in that sending to the web server on one of the four identified in accordance with the file type The content distribution apparatus described. A function for storing a correspondence between a web page and a web server that provides the web page;
A web page on which new content is to be posted, a content group to which new content is to be posted, among the content groups constituting each of a plurality of partial areas forming the web page, and new content on the web page The ability to centrally accept registration requests for new content from the content creator,
Generate a distribution file that aggregates new content for each content group specified in the registration request and for each start date in order to start posting multiple new contents with the same start date on the web server at the same time. A function that associates the distribution file with data indicating the date and time of publication,
In order to prevent the content creator from having to be aware of the web server where the new content is actually placed, the web server where the new content included in the distribution file is placed is identified with reference to the correspondence relationship , A function for associating data indicating the specified web server with the distribution file;
For multiple distribution files that are associated with the same publication start date and time, specify the arrangement order that defines the order in which new content in each distribution file is arranged on the web server, and place each distribution file on each distribution file A function for associating data indicating the order;
Asynchronously with the registration request, a distribution unit that identifies a web server to be arranged with reference to data associated with the distribution file, and transmits the distribution file to the identified web server;
A computer program for realizing a computer.

Images