Proteins, pools, and slawx in processing environments

• US 8,407,725 B2
• Filed: 04/24/2008
• Issued: 03/26/2013
• Est. Priority Date: 04/24/2007
• Status: Active Grant

• Current Assignee: Oblong Industries, Inc. (Oblong, Inc.)
• Original Assignee: Oblong Industries, Inc. (Oblong, Inc.)
• Inventors: Kramer, Kwindla Hultman, Underkoffler, John S.
• Primary Examiner(s): Anya, Charles E
• Application Number:
  US12/109,263
• Publication Number:
  US 20080271053A1
• Time in Patent Office: 1,797 Days
• Field of Search: 718/106, 719/318
• US Class Current: 719/318
• CPC Class Codes: G06F 9/451 Execution arrangements for user interfaces
• CPC Class Codes: G06F 9/542 Event management; Broadcasting; Multicasting; Notifications
• CPC Class Codes: G06F 9/544 Buffers; Shared memory; Pipes

Abstract

Embodiments described herein include mechanisms for encapsulating data that needs to be shared between or across processes. These mechanisms include slawx (plural of “slaw”), proteins, and pools. Generally, slawx provide the lowest-level of data definition for inter-process exchange, proteins provide mid-level structure and hooks for querying and filtering, and pools provide for high-level organization and access semantics. Slawx includes a mechanism for efficient, platform-independent data representation and access. Proteins provide a data encapsulation and transport scheme using slawx as the payload. Pools provide structured and flexible aggregation, ordering, filtering, and distribution of proteins within a process, among local processes, across a network between remote or distributed processes, and via longer term (e.g. on-disk, etc.) storage.

Claims

1. A method comprising:

detecting an event of a source device;

generating at least one data sequence comprising device event data specifying the event and state information of the event, wherein the device event data and state information are type-specific data having a type corresponding to an application of the source device; and

forming a data capsule to include the at least one data sequence, the data capsule having a data structure comprising an application-independent representation of the at least one data sequence;

transferring the data capsule from a first application having a first application type to at least one second application having at least one second application type, wherein the first application type is different than the second application type, wherein the generating of the at least one data sequence was executed by the first application; and

maintaining intact the at least one data sequence of the data capsule during the transferring.

2. The method of claim 1, wherein the generating of the at least one data sequence comprises:

generating a first respective data set that includes first respective device event data;

generating a second respective data set that includes second respective state information; and

forming a first data sequence to include the first respective data set and the second respective data set.

3. The method of claim 2, wherein the generating of the first respective data set includes forming the first respective data set to include identification data of the source device, the identification data including data identifying the source device.

4. The method of claim 2, wherein the generating of the at least one data sequence comprises:

generating a first respective data set that includes first respective device event data;

generating a second respective data set that includes second respective state information; and

forming a second data sequence to include the first respective data set and the second respective data set.

5. The method of claim 4, wherein the generating of the first respective data set includes generating a first respective data set offset, wherein the first respective data set offset points to the first respective data set of the second data sequence.

6. The method of claim 4, wherein the generating of the second respective data set includes generating a second respective data set offset, wherein the second respective data set offset points to the second respective data set of the second data sequence.

7. The method of claim 2, wherein the first respective data set is a description list, the description list including a description of the data.

8. The method of claim 1, wherein the device event data is a tagged byte-sequence representing typed data.

9. The method of claim 8, wherein the device event data includes a type header and a type-specific data layout.

10. The method of claim 1, wherein the state information is a tagged byte-sequence representing typed data.

11. The method of claim 10, wherein the state information includes a type header and a type-specific data layout.

12. The method of claim 1, comprising:

generating at least one offset; and

forming the data capsule to include the at least one offset.

13. The method of claim 12, comprising:

generating a first offset having a first variable length;

wherein the first offset points to the device event data of a first data sequence of the at least one data sequence.

14. The method of claim 12, comprising:

generating a second offset having a second variable length;

wherein the second offset points to the state information of a first data sequence of the at least one data sequence.

15. The method of claim 12, comprising:

forming a first code path through the data capsule using a first offset of the at least one offset;

forming a second code path through the data capsule using a second offset of the at least one offset;

wherein the first code path and the second code path are different paths.

16. The method of claim 12, wherein at least one of the first offset and the second offset include metadata, the metadata comprising context-specific metadata corresponding to a context of the application.

17. The method of claim 1, comprising:

generating a header that includes a length of the data capsule;

forming the data capsule to include the header.

18. The method of claim 1, comprising transferring the data capsule to a repository.

19. The method of claim 18, comprising:

detecting a second event of a second source device;

searching the repository for data capsules corresponding to the second event.

20. The method of claim 19, comprising:

identifying a correspondence between the data capsule and the second event;

extracting the data capsule from the repository in response to the identifying; and

executing on behalf of the second source device a processing operation corresponding to the second event on behalf of the second source device in response to contents of the data capsule, wherein the source device corresponds to an application of a first type and the second source device corresponds to a second application of a second type.

21. The method of claim 18, wherein the repository is coupled to a plurality of applications, the repository including a plurality of data capsules corresponding to the plurality of applications, the repository providing access to the plurality of data capsules by the plurality of applications, wherein the plurality of applications include at least the first application and the second application, wherein at least two applications of the plurality of applications are different applications.

22. The method of claim 18, wherein the repository provides state caching of a plurality of data capsules.

23. The method of claim 18, wherein the repository provides linear sequencing of a plurality of data capsules.

24. The method of claim 1, wherein the data structure is untyped.

25. The method of claim 1, wherein the data structure of the data capsule provides a platform-independent representation of the device event data and the state information.

26. The method of claim 1, wherein the data structure of the data capsule provides platform-independent access to the device event data and the state information.

27. The method of claim 1, comprising using the at least one data sequence during operations of the second application.

28. The method of claim 1, wherein the event comprises a user interface event.

29. The method of claim 1, wherein the event comprises a graphics event.

30. The method of claim 1, wherein the event comprises depositing of state information.