Techniques for metadata-driven dynamic content serving

US9276995B2 · US · B2

Patent metadata
FieldValue
Publication numberUS-9276995-B2
Application numberUS-201514592804-A
CountryUS
Kind codeB2
Filing dateJan 8, 2015
Priority dateDec 3, 2010
Publication dateMar 1, 2016
Grant dateMar 1, 2016

How to read this patent

A practical reading order for non-experts. Skip the full description unless you need deep technical detail.

  1. Title

    What the patent document calls the invention.

  2. Abstract

    A short plain-language summary of the technical disclosure.

  3. Assignees and inventors

    Who owns or filed the patent and who is credited as inventor.

  4. Key dates

    Filing, priority, publication, and grant dates set the timeline.

  5. First independent claim

    The legal scope of protection — read this for what is actually claimed.

  6. CPC / IPC classifications

    Technology tags used to group this patent with similar filings.

  7. Citations and related patents

    Prior art links and similar publications in this corpus.

Abstract

Official abstract text for this publication.

Techniques for metadata-driven dynamic content serving. Metadata content is stored as a source instance, the metadata content is to be utilized to provide dynamically-constructed pages of content. The metadata content is published to one or more runtime pods communicatively coupled to receive the metadata content. A request for content is received with a selected one of the one or more runtime pods. Content is provided in response to the request as a response with the selected runtime pod utilizing the metadata content published from the source instance.

First claim

Opening claim text (preview).

What is claimed is: 1. A method comprising: storing metadata content as a source instance, the metadata content to be utilized to provide dynamically-constructed pages of content, wherein the metadata comprises at least a site definition stored according to a site identifier to allow the metadata to be retrieved and converted to a format indicated by a request; publishing the metadata content to one or more runtime pods communicatively coupled to receive the metadata content, wherein the source instance comprises a metadata definition repository and is a primary source of dynamic data for serving pages in the runtime pods, wherein the runtime pods are groups of multiple servers that act as a single entity to dynamically generate metadata-driven content in response to requests received from client devices; receiving a request for content with a selected one of the one or more runtime pods for a specific site; mapping the specific site to a tenant identifier corresponding to a tenant of a multitenant environment; using the tenant identifier to retrieve site metadata from a site metadata server within the multitenant environment; providing content in response to the request as a response with the selected runtime pod utilizing the metadata content. 2. The method of claim 1 wherein the one or more runtime pods operate within a multitenant database environment, wherein the multitenant database environment stores data for multiple client entities each identified by a tenant identifier (ID) having one of one or more users associated with the tenant ID, wherein users of each of multiple client entities can only access data identified by a tenant ID associated with the respective client entity, and wherein the multitenant database is a hosted database provided by an entity separate from the client entities, and provides on-demand database service to the client entities. 3. The method of claim 2 wherein the multitenant environment comprises at least two runtime pods. 4. The method of claim 1 further comprising: mapping a source of the request to a tenant ID corresponding to the source; retrieving metadata corresponding to the tenant ID; generating the response with a render engine based on the metadata. 5. The method of claim 1 wherein the runtime pod comprises at least one proxy server, at least one application server and at least one database server. 6. The method of claim 5 wherein the runtime pod further comprises at least one firewall and at least one load balancer. 7. An apparatus comprising: means for storing metadata content as a source instance, the metadata content to be utilized to provide dynamically-constructed pages of content, wherein the metadata comprises at least a site definition stored according to a site identifier to allow the metadata to be retrieved and converted to a format indicated by a request; means for publishing the metadata content to one or more runtime pods communicatively coupled to receive the metadata content, wherein the source instance comprises a metadata definition repository and is a primary source of dynamic data for serving pages in the runtime pods, wherein the runtime pods are groups of multiple servers that act as a single entity to dynamically generate metadata-driven content in response to requests received from client devices; means for receiving a request for content with a selected one of the one or more runtime pods for a specific site; means for mapping the specific site to a tenant identifier corresponding to a tenant of a multitenant environment; means for using the tenant identifier to retrieve site metadata from a site metadata server within the multitenant environment; means for providing content in response to the request as a response with the selected runtime pod utilizing the metadata content. 8. The method of claim 7 further comprising: means for mapping a source of the request to a tenant ID corresponding to the source; means for retrieving metadata corresponding to the tenant ID; means for generating the response with a render engine based on the metadata. 9. An article comprising a non-transitory computer-readable medium having instructions stored thereon that, when executed by one or more processors, cause the one or more processors to: store metadata content as a source instance, the metadata content to be utilized to provide dynamically-constructed pages of content, wherein the metadata comprises at least a site definition stored according to a site identifier to allow the metadata to be retrieved and converted to a format indicated by a request; publish the metadata content to one or more runtime pods communicatively coupled to receive the metadata content, wherein the source instance comprises a metadata definition repository and is a primary source of dynamic data for serving pages in the runtime pods, wherein the runtime pods are groups of multiple servers that act as a single entity to dynamically generate metadata-driven content in response to requests received from client devices; receive a request for content with a selected one of the one or more runtime pods for a specific site; map the specific site to a tenant identifier corresponding to a tenant of a multitenant environment; use the tenant identifier to retrieve site metadata from a site metadata server within the multitenant environment; provide content in response to the request as a response with the selected runtime pod utilizing the metadata content. 10. The article of claim 9 wherein the one or more runtime pods operate within a multitenant database environment, wherein the multitenant database environment stores data for multiple client entities each identified by a tenant identifier (ID) having one of one or more users associated with the tenant ID, wherein users of each of multiple client entities can only access data identified by a tenant ID associated with the respective client entity, and wherein the multitenant database is a hosted database provided by an entity separate from the client entities, and provides on-demand database service to the client entities. 11. The article of claim 10 wherein the multitenant environment comprises at least two runtime pods. 12. The article of claim 9 further comprising instructions that, when executed, cause the one or more processors to: map a source of the request to a tenant ID corresponding to the source; retrieve metadata corresponding to the tenant ID; generate the response with a render engine based on the metadata. 13. The article of claim 9 wherein the runtime pod comprises at least one proxy server, at least one application server and at least one database server. 14. The article of claim 13 wherein the runtime pod further comprises at least one firewall and at least one load balancer.

Assignees

Inventors

Classifications

  • H04L67/02Primary

    based on web technology, e.g. hypertext transfer protocol [HTTP] · CPC title

  • for remote control or remote monitoring of applications · CPC title

  • in which an application is distributed across nodes in the network (software deployment G06F8/60; multiprogramming arrangements G06F9/46) · CPC title

  • G06F16/958Primary

    Organisation or management of web site content, e.g. publishing, maintaining pages or automatic linking · CPC title

  • Physics · mapped topic

Patent family

Related publications grouped by family.

External sources

Frequently asked questions

Answers are generated from the same data shown on this page.

What does patent US9276995B2 cover?
Techniques for metadata-driven dynamic content serving. Metadata content is stored as a source instance, the metadata content is to be utilized to provide dynamically-constructed pages of content. The metadata content is published to one or more runtime pods communicatively coupled to receive the metadata content. A request for content is received with a selected one of the one or more runtime …
Who is the assignee on this patent?
Salesforce Com Inc
What technology area does this patent fall under?
Primary CPC classification H04L67/02. Mapped technology areas include Electricity.
When was this patent published?
Publication date Tue Mar 01 2016 00:00:00 GMT+0000 (Coordinated Universal Time) (B2). Legal status and post-grant events are not shown on this page.
What related patents are in patentsdb?
We list 8 related publications on this page (citations in our corpus or others sharing the same primary CPC).