Method and apparatus for polymorphic serialization

• US 9,026,583 B2
• Filed: 09/19/2011
• Issued: 05/05/2015
• Est. Priority Date: 09/17/2010
• Status: Active Grant

• Current Assignee: Oracle International Corporation (Oracle Corporation)
• Original Assignee: Oracle International Corporation (Oracle Corporation)
• Inventors: Carter, Wayne, Tadepalli, Sridhar, Yaseen, Rahim
• Primary Examiner(s): KHAN, AFTAB N
• Application Number:
  US13/235,729
• Publication Number:
  US 20120072477A1
• Time in Patent Office: 1,324 Days
• Field of Search: 709/219, 709/203, 709/209, 707/803, 707/809, 707/810, 707/811, 707/755, 707/756
• US Class Current: 709/203
• CPC Class Codes: G06F 16/258 Data format conversion from or to a database
• CPC Class Codes: G06F 16/9577 Optimising the visualization of content, e.g. distillation of HTML documents
• CPC Class Codes: G06F 16/972 Access to data in other repository systems, e.g. legacy data or dynamic Web page generation
• CPC Class Codes: H04M 1/72469 for operating the device by selecting functions from two or more displayed items, e.g. menus or icons

Abstract

Polymorphic serialization is disclosed. In one embodiment polymorphic serialization may include generating a first reply in response to receiving a first request from a first device, the first reply including first content in a first serialization format. The first reply is transmitted to the first device via a first communication link. A second reply may be generated in response to receiving a second request from a second device, the second reply including second content in a second serialization format. The second reply is transmitted to the second device via a second communication link. The first and second devices are distinct from each other, and the first and second serialization formats are distinct from each other.

Claims

1. A method comprising:

in response to receiving a first request from a first device configured to receive replies that are serialized in a first format, determining a first reply by a CRM application executing on a server device comprising at least one processor, wherein the CRM application comprises an application definition;

generating the first reply as a function of a portion of the application definition, wherein the portion of the application definition comprises a page definition used to render a page with icons arranged in a two-dimensional pattern, data in a list pattern, or data in a form pattern;

in response to receiving a second request from a second device configured to receive replies that are serialized in a second format that is distinct from the first format, determining a second reply by the CRM application;

generating the second reply as a function of the portion of the application definition;

wherein the portion of the application definition comprises a plurality of tags and a plurality of tag designators, wherein the plurality of tag designators indicates whether the plurality of tags, respectively, are designated as one of a first type of tag, a second type of tag, and a third type of tag;

wherein generating the first reply comprises;

serializing a first tag of the page definition in accordance with a first process when the first tag is designated by a first tag designator as the first type of tag;

serializing the first tag in accordance with a second process when the first tag is designated by the first tag designator as the second type of tag;

serializing the first tag in accordance with a third process when the first tag is designated by the first tag designator as the third type of tag;

wherein generating the second reply comprises;

serializing the first tag in accordance with a fourth process when the first tag is designated by the first tag designator as the first type of tag;

serializing the first tag in accordance with a fifth process when the first tag is designated by the first tag designator as the second type of tag;

serializing the first tag in accordance with a sixth process when the first tag is designated by the first tag designator as the third type of tag.

2. The method of claim 1:

wherein the first request comprises data that directly or indirectly indicates that the first device is configured to deserialize replies in a first serialization format;

wherein the second request comprises data that directly or indirectly indicates that the second device is configured to deserialize replies in a second serialization format.

3. The method of claim 1 wherein the first reply lacks the plurality of tag designators, and wherein the second reply lacks the plurality of tag designators.

4. The method of claim 1 wherein the first format is JSON, and wherein the second format is plist.

5. The method of claim 1:

wherein the first reply is generated as a function of first data;

wherein the second reply is generated as a function of the first data.

6. The method of claim 5 further comprising:

the first device deserializing the first reply in response to the first device receiving the first reply;

the first device displaying a first page in response to the first device deserializing the first reply;

the second device deserializing the second reply in response to the second device receiving the second reply;

the second device displaying a second page in response to the second device deserializing the second reply;

wherein the first and second pages are visually distinctive.

7. The method of claim 5 further comprising:

the first device deserializing the first reply in response to the first device receiving the first reply;

the first device displaying a first page in response to the first device deserializing the first reply;

wherein the first page comprises visual representations of the first data and a visual representation of a first component defined in the portion of the application definition.

8. The method of claim 7 further comprising:

the second device deserializing the second reply in response to the second device receiving the second reply;

the second device displaying a second page in response to the second device deserializing the second reply;

wherein the second page comprises visual representations of the first data but not a visual representation of the first component defined in the portion of the application definition.

9. A non-transitory computer readable medium comprising instructions executable by a computer system, wherein the computer system implements a method in response to executing the instructions, the method comprising:

in response to receiving a first request from a first device configured to receive replies that are serialized in a first format, determining a first reply by a CRM application executing on a server device comprising at least one processor, wherein the CRM application comprises an application definition;

generating the first reply as a function of a portion of the application definition, wherein the portion of the application definition comprises a page definition used to render a page with icons arranged in a two-dimensional pattern, data in a list pattern, or data in a form pattern;

in response to receiving a second request from a second device configured to receive replies that are serialized in a second format that is distinct from the first format, determining a second reply by the CRM application;

generating the second reply as a function of the portion of the application definition;

wherein the portion of the application definition comprises a plurality of tags and a plurality of tag designators, wherein the plurality of tag designators indicates whether the plurality of tags, respectively, are designated as one of a first type of tag, a second type of tag, and a third type of tag;

wherein generating the first reply comprises;

serializing a first tag of the page definition in accordance with a first process when the first tag is designated by a first tag designator as the first type of tag;

serializing the first tag in accordance with a second process when the first tag is designated by the first tag designator as the second type of tag;

serializing the first tag in accordance with a third process when the first tag is designated by the first tag designator as the third type of tag;

wherein generating the second reply comprises;

serializing the first tag in accordance with a fourth process when the first tag is designated by the first tag designator as the first type of tag;

serializing the first tag in accordance with a fifth process when the first tag is designated by the first tag designator as the second type of tag;

serializing the first tag in accordance with a sixth process when the first tag is designated by the first tag designator as the third type of tag.

10. The non-transitory computer readable medium of claim 9:

wherein the first reply is generated as a function of first data;

wherein the second reply is generated as a function of the first data.

11. The non-transitory computer readable medium of claim 9:

wherein the first request comprises data that directly or indirectly indicates that the first device is configured to deserialize replies in a first serialization format;

wherein the second request comprises data that directly or indirectly indicates that the second device is configured to deserialize replies in a second serialization format.

12. A method comprising:

transmitting instructions to a server device for storage therein, wherein the server device is configured to implement a method in response to executing the instructions, the method comprising;

in response to receiving a first request from a first device configured to receive replies that are serialized in a first format, determining a first reply by a CRM application executing on the server device comprising at least one processor, wherein the CRM application comprises an application definition;

generating the first reply as a function of a portion of the application definition, wherein the portion of the application definition comprises a page definition used to render a page with icons arranged in a two-dimensional pattern, data in a list pattern, or data in a form pattern;

in response to receiving a second request from a second device configured to receive replies that are serialized in a second format that is distinct from the first format, determining a second reply by the CRM application;

generating the second reply as a function of the portion of the application definition;

wherein the portion of the application definition comprises a plurality of tags and a plurality of tag designators, wherein the plurality of tag designators indicates whether the plurality of tags, respectively, are designated as one of a first type of tag, a second type of tag, and a third type of tag;

wherein generating the first reply comprises;

serializing a first tag of the page definition in accordance with a first process when the first tag is designated by a first tag designator as the first type of tag;

serializing the first tag in accordance with a second process when the first tag is designated by the first tag designator as the second type of tag;

serializing the first tag in accordance with a third process when the first tag is designated by the first tag designator as the third type of tag;

wherein generating the second reply comprises;

serializing the first tag in accordance with a fourth process when the first tag is designated by the first tag designator as the first type of tag;

serializing the first tag in accordance with a fifth process when the first tag is designated by the first tag designator as the second type of tag;

serializing the first tag in accordance with a sixth process when the first tag is designated by the first tag designator as the third type of tag.