Home
Patent Search
IMT Blog
REGISTER
|
SIGN IN
United States Patent Application
20020138582
Kind Code
A1
Chandra, Mala ; et al.
September 26, 2002
Methods and apparatus providing electronic messages that are linked and aggregated
Abstract
A method for associating related electronic messages in computer storage. A first transportable application is created and stored. User input requesting creation of a link from the first transportable application to another transportable application is received. User input that selects a second transportable application from among a plurality of previously created transportable applications is received. A link from the first transportable application to the second transportable application is created and stored. As a result, transportable application may be inter-related in complex message webs. The message webs may also be inter-related in message web rings. Links may be generated manually or automatically, based on context, workflow processes, or other known relationships among applications. Recipient lists and data may propagate among fields of linked transportable applications, directly or according to abstract business rules. Further, multiple-part electronic messages are disclosed. A graphical user interface of an electronic messaging system displays a message in the form of one or more header portions and one or more body portions. Each of the body portions has a selection region. While one body portion is visible at a given time, all the selection regions are continuously visible in the user interface to facilitate selection of any of the body portions at a particular time. Selecting a selection region of a non-displayed body portion causes a server to generate a refreshed user interface that includes the entirety of the selected body portion, and that hides the previously viewed body portion. As a result, a large amount of associated information may be combined in a single message in a way that is clearly organized and easily accessible.
Inventors:
Chandra; Mala
(Pleasanton, CA)
, Evans; Steven R.
(Los Altos Hills, CA
)
, Kruempelstaedter; John
(Cupertino, CA
)
, Khalsa; Kirpal
(Sunnyvale, CA
)
, McFarland; Joshua
(San Francisco, CA
)
Correspondence Name and Address:
1600 WILLOW STREET
HICKMAN, PALERMO, TRUONG & BECKER
SAN JOSE
CA
95125
US
Series Code:
948051
Filed:
September 5, 2001
U.S. Current Class:
709/206
U.S. Class at Publication:
709/206
Intern'l Class:
G06F 015/16
Claims
What is claimed is:
1. A method for processing a request to display an electronic message, the method comprising the computer-implemented steps of: generating first message data, wherein the first message data defines at least a first message portion and one or more selection regions for one or more other message portions of a multiple-part electronic message having a plurality of message portions; providing the first message data to a client; receiving from the client a request for a second portion of the electronic message selected from among the other message portions; generating second message data which, when processed at a user interface of the client, causes the client to display the second portion of the electronic message; and providing the second message data to the client.
2. A method as recited in claim 1, wherein generating first message data further comprises the steps of generating first message data that defines a plurality of message portions each having a corresponding selection region and that defines a message user interface region that comprises all corresponding selection regions and the first message portion.
3. A method as recited in claim 1, wherein the first message data includes user interface definition data which, when processed at the user interface, causes the user interface to display the first portion of the electronic message in a first panel.
4. A method as recited in claim 3, wherein the user interface definition data includes data which, when processed at the user interface, causes the user interface to display a first identifier of the first portion of the electronic message in the first panel.
5. A method as recited in claim 4, wherein the first identifier indicates content of the first portion of the electronic message.
6. A method as recited in claim 3, wherein generating the first message data and generating the second message data further comprises the steps of generating second user interface definition data which, when processed at the user interface, causes the user interface to display a plurality of continuously visible selection regions, each associated with a different portion of the multiple-part message and the first portion of the electronic message.
7. A method as recited in claim 6, wherein the second user interface definition data comprises data which, when processed at the user interface, causes one or more other identifiers to be displayed in association with the continuously visible selection regions to identify corresponding portions of the electronic message.
8. A method as recited in claim 1, wherein the first message data comprises selection region definition data which, when processed at the user interface of the client, causes the client to display a plurality of selection regions that extend outwardly laterally from the first portion of the electronic message.
9. A method as recited in claim 1, wherein the first message data comprises selection region definition data which, when processed at the user interface of the client, causes the client to display a plurality of selection regions that extend outwardly upwardly from the first portion of the electronic message.
10. A method as recited in claim 1, wherein the second message data comprises selection region definition data which, when processed at the user interface of the client, causes the client to display a plurality of selection regions that extend outwardly downwardly from the first portion of the electronic message.
11. A method as recited in claim 1, wherein the first message data and the second message data comprise one or more hypertext markup language (HTML) instructions.
12. A method as recited in claim 1, wherein the first message data comprises selection region definition data which, when processed at the user interface of the client, causes the client to display a toolbar of functions for manipulating the multiple-part electronic message within a user interface panel that contains the first message portion.
13. A method as recited in claim 1, wherein the first message data further comprises one or more executable application building blocks, and further comprising the steps of: executing the one or more application building blocks to result in creating and storing one or more then-current dynamic data values as part of the first message portion; providing the one or more dynamic data values to the client as part of the first message portion.
14. A method as recited in claim 1, further comprising the steps of: retrieving one or more then-current dynamic data values from a database; rendering the dynamic data values as part of the first message portion; providing the one or more dynamic data values to the client as part of the first message portion.
15. A method as recited in claim 1, wherein the step of generating first message data comprises the steps of generating first message data that defines at least a first message page, one or more selection regions for one or more other message pages of a multiple-page electronic message having a plurality of message pages, and a plurality of sub-pages of the first message page.
16. A method as recited in claim 15, further comprising the steps of: receiving a selection of a sub-page of the first message page; generating third message data that defines the selected sub-page of the first message page and which, when processed at the user interface, causes the user interface to display the selected sub-page of the electronic message; providing the third message data to the client.
17. A method providing a multiple-part electronic message, the method comprising the computer-implemented steps of: generating first message data that defines a multiple-part electronic message and includes at least a first message portion and one or more selection regions for one or more other associated message portions; providing the first message data to a first client; receiving a request to forward the multiple-part electronic message to a recipient; in response to receiving the request, generating second message data to the recipient that defines the multiple-part electronic message; and providing the second message data to the second client.
18. A method of asynchronously dynamically updating information of a multiple-part electronic message, the method comprising the computer-implemented steps of: generating first message data, wherein the first message data defines at least a first message portion having a dynamic content region and one or more selection regions for one or more other message portions of a multiple-part electronic message having a plurality of message portions; providing the first message data to a first client; receiving one or more asynchronous updates to the dynamic content region; generating second message data that defines the first message portion, the dynamic content region including the one or more updates, and the one or more selection regions; and providing the second message data to a second client.
19. A method as recited in claim 18, further comprising the steps of: receiving a selection of a second portion of the electronic message selected from among the other message portions; retrieving then-current dynamic content for a second dynamic content region of the second portion of the electronic message; generating third message data that defines the second portion of the electronic message and that includes the then-current dynamic content for the second dynamic content region; providing the third message data to the client.
20. A method for processing; data at a user interface comprising the computer-implemented steps of: receiving a request to display an electronic message; in response to receiving the request to display an electronic message, requesting a first portion of an electronic message; receiving first message data; and processing the first message data to cause the first portion of the electronic message to be displayed on the user interface.
21. A method as recited in claim 20, further comprising the computer-implemented steps of: receiving a request to display a second portion of the electronic message; in response to the request to display a second portion of the electronic message, requesting the second portion of the electronic message; receiving second message data; and processing the second message data to cause the second portion of the electronic message to be displayed on the user interface.
22. A method as recited in claim 20, further comprising the computer-implemented steps of: receiving user interface object data; and processing the user interface object data to cause a user interface object to be displayed on the user interface; and wherein the step of receiving a request to display a second portion of the electronic mail message receiving second message data includes detecting user manipulation of the user interface object.
23. A method as recited in claim 20, wherein the method further comprises the computer-implemented steps of: receiving user interface object data; and processing the user interface object data to cause a user interface object to be displayed in association with a second portion of the electronic mail message that is not displayed concurrently with the first portion of the electronic mail message.
24. A method as recited in claim 20, wherein the first portion of the electronic mail message is displayed on a panel.
25. A data processing apparatus comprising: a memory device configured to store electronic message data; a processor communicatively coupled to the memory device; and one or more sequences of instructions in the memory device which, when executed by the processor, cause the processor to carry out the steps of: generating first message data, wherein the first message data defines at least a first message portion and one or more selection regions for one or more other message portions of a multiple-part electronic message having a plurality of message portions; providing the first message data to a client; receiving from the client a request for a second portion of the electronic message selected from among the other message portions; generating second message data which, when processed at a user interface of the client, causes the client to display the second portion of the electronic message; and providing the second message data to the client.
26. An apparatus for processing a request to display an electronic message, comprising: means for generating first message data, wherein the first message data defines at least a first message portion and one or more selection regions for one or more other message portions of a multiple-part electronic message having a plurality of message portions; means for providing the first message data to a client; means for receiving from the client a request for a second portion of the electronic message selected from among the other message portions; means for generating second message data which, when processed at a user interface of the client, causes the client to display the second portion of the electronic message; and means for providing the second message data to the client.
27. A computer-readable medium comprising one or more sequences of instructions for processing a request to display an electronic message, which instructions, when executed by one or more processors, cause the one or more processors to carry out the steps of: generating first message data, wherein the first message data defines at least a first message portion and one or more selection regions for one or more other message portions of a multiple-part electronic message having a plurality of message portions; providing the first message data to a client; receiving from the client a request for a second portion of the electronic message selected from among the other message portions; generating second message data which, when processed at a user interface of the client, causes the client to display the second portion of the electronic message; and providing the second message data to the client.
28. A method for associating related electronic messages in computer storage, the method comprising the computer-implemented steps of: creating and storing a first transportable application; receiving user input requesting creation of a link from the first transportable application to another transportable application; receiving user input that selects a second transportable application from among a plurality of previously created transportable applications; and creating and storing a link from the first transportable application to the second transportable application.
29. A method as recited in claim 28, wherein the step of creating and storing a link comprises the steps of: creating and storing an asynchronously dynamically updated list of references to other transportable applications in association with the first transportable application; creating and storing a reference to the second transportable application in the list of references.
30. A method as recited in claim 28, wherein the step of creating and storing a link comprises the steps of: creating and storing an asynchronously dynamically updated List building block in association with the first transportable application; creating and storing a reference to the second transportable application in the list building block.
31. A method as recited in claim 28, wherein the step of receiving user input that selects a second transportable application comprises the steps of receiving user input that copies a URL of the second transportable application and receiving user input that pastes the URL into the first transportable application in a region associated with the list.
32. A method as recited in claim 28, wherein the step of receiving user input that selects a second transportable application comprises the steps of receiving user input that drags a representation of the second transportable application into the first transportable application in a region associated with the list.
33. A method as recited in claim 28, further comprising the step s of applying one or more access controls to the link, wherein the access controls specify that one or more users or groups may not access the second transportable application using the link.
34. A method of associating related electronic messages in computer storage, the method comprising the computer-implemented steps of: creating and storing a first transportable application; automatically creating and storing a second transportable application as a result of a workflow process or event associated with the first transportable application; and creating and storing a link from the first transportable application to the second transportable application.
35. A method as recited in claim 34, wherein the step of creating and storing a link comprises the steps of: creating and storing an asynchronously dynamically updated list of references to other transportable applications in association with the first transportable application; creating and storing a reference to the second transportable application in the list of references.
36. A method as recited in claim 34, wherein the step of creating and storing a link comprises the steps of: creating and storing an asynchronously dynamically updated List building block in association with the first transportable application; creating and storing a reference to the second transportable application in the list building block.
37. A method as recited in claim 34, further comprising the steps of prompting a user associated with the first transportable application to confirm whether to link the first transportable application to the second transportable application; and carrying out the step of creating and storing a link only in response to receiving user input that confirms that the first transportable application should link to the second transportable application.
38. A method as recited in claim 34, further comprising the steps of applying one or more access controls to the link, wherein the access controls specify that one or more users or groups may not access the second transportable application using the link.
39. A method for associating related electronic messages in computer storage, the method comprising the computer-implemented steps of: creating and storing a first transportable application; creating and storing a link from the first transportable application to a second transportable application; determining that a programmatic object associated with the first transportable application is new, updated or deleted; in response thereto, modifying the link in accordance with the new, updated or deleted object.
40. A method as recited in claim 39, wherein the step of modifying the link in response to an updated object comprises the steps of identifying all other transportable applications that are linked to the first transportable application and that reference the updated object, and modifying all references to the updated object.
41. A method as recited in claim 39, wherein the object comprises a content element of the transportable application, and further comprising the steps of searching the content element for one or more recognizable object references, and creating one or more links relating to the recognizable object references in a list of automatically generated links.
42. A method as recited in claim 41, wherein the object reference comprises an e-mail address or user name, and wherein the step of creating links relating to the object references comprises creating a mail link in the list which, when selected by a user, generates an e-mail message to the address or user name.
43. A method as recited in claim 41, wherein the object reference comprises a Uniform Resource Locator, and wherein the step of creating links relating to the object references comprises creating a URL link in the list which, when selected by a user, generates a display of a hypertext document identified by the URL.
44. A method as recited in claim 41, wherein the object reference comprises a title of a third transportable application, and wherein the step of creating links relating to the object references comprises creating a link in the list to the third transportable application.
45. A method of associating related electronic messages in computer storage, the method comprising the computer-implemented steps of: receiving user input associated with completing a task in a first transportable application; generating a list of one or more other transportable applications that are likely to follow the first transportable application in a workflow or business process associated with the first transportable application, based on relevance of the other transportable applications to a context of the first transportable application; requesting user input that specifies whether to link one or more of the other transportable applications to the first transportable application; and creating and storing one or more links from the first transportable application to one or more of the other transportable applications.
46. A method of displaying a message that contains an embedded HTML document, comprising the computer-implemented steps of: receiving a transportable application, which comprises an embedded HTML document, in an e-mail client application; displaying the embedded HTML document in a graphical window of the e-mail client application; displaying one or more graphical navigation buttons in association with the graphical window; receiving user input that selects one or more of the graphical navigation buttons; and displaying one or more other HTML documents in the graphical window in response to the user input.
47. A method as recited in claim 46, wherein each of the graphical navigation buttons is associated with client-executable computer program code, and wherein the step of displaying one or more other documents comprises the step of executing one or more instructions of the computer program code that are associated with one of the selected graphical navigation buttons that is selected by the user input.
48. A method as recited in claim 46, wherein each of the graphical navigation buttons is associated with client-executable JavaScript code, and wherein the step of displaying one or more other HTML documents comprises the step of executing a portion of the JavaScript that is associated with one of the selected graphical navigation buttons that is selected by the user input.
49. A method of associating a plurality of sets of related electronic messages in computer storage, the method comprising the computer-implemented steps of: creating and storing a first set of a plurality of linked transportable applications; creating and storing a second set of a plurality of linked transportable applications; designating a first transportable application among the first set as a home transportable application for the first set; designating a second transportable application among the second set as a home transportable application for the second set; creating and storing, in association with the home transportable application of the first set, a next link that identifies the home transportable application of the second set; creating and storing, in association with the home transportable application of the second set, a previous link that identifies the home transportable application of the first set.
50. A method as recited in claim 49, wherein the first set comprises a first message web, the second set comprises a second message web, and the links among the first message web and the second message web associate the first message web with the second message web in a message web ring.
51. A method as recited in claim 49, further comprising the steps of: creating and storing a third set of a plurality of linked transportable applications having a third home transportable application; modifying the next link and the previous link of the first set and second set such that the third set of transportable application is logically inserted between the first set and the second set.
52. A method of generating a list of recipients for a first message that is linked to a second message, comprising the computer-implemented steps of: creating and storing a first transportable application that is linked to a second transportable application; creating a first recipient list in association with the first transportable application, wherein the first recipient list identifies one or more users or groups to whom the first transportable application is directed; creating a second recipient list in association with the second transportable application, wherein the second recipient list comprises at least one reference to the first recipient list; automatically resolving the at least one reference into a second list of one or more users or groups to whom the second transportable application is directed.
53. A method as recited in claim 52, wherein the second recipient list further comprises at least one expression that identifies one or more users or groups to add or delete from the referenced first recipient list, and further comprising the steps of automatically determining a second list of one or more users or groups to whom the second transportable application is directed by resolving the at least one reference and applying the at least one expression.
54. A method of propagating data from a first message to a second message that is linked to the first message, comprising the computer-implemented steps of: creating and storing a first transportable application that is linked to a second transportable application; creating and storing a reference, in a first data field of the first transportable application, to a second data field of the second transportable application; determining that the first data field of the second transportable application is changed; automatically creating and storing the second data field of the second transportable application in the first data field of the first transportable application.
55. A method as recited in claim 54, wherein the steps of determining and automatically creating comprise the steps of: determining whether the first data field of the first transportable application comprises a link to a second data field; verifying that the second data field comprises up-to-date data; retrieving data from the second data field; storing the retrieved data in the first data field.
56. A method as recited in claim 55, further comprising the steps of: determining whether any other transportable applications are subscribed to the first data field; carrying out the step of automatically creating and storing the second data field only for each transportable application that is subscribed to the first data field.
Description
CROSS-REFERENCE TO RELATED APPLICATIONS
[0001] Domestic priority is claimed under 35 U.S.C. 119(e) from prior Provisional application Ser. No. 60/230,037, filed Sep. 5, 2000, the entire contents of which are hereby incorporated by reference as if fully set forth herein.
FIELD OF INVENTION
[0002] The present invention generally relates to data processing in the fields of electronic messaging and collaborative communications. The invention relates more specifically to a collaborative communications system providing transportable applications, multiple-page electronic messages and electronic messages that are linked and aggregated.
BACKGROUND OF THE INVENTION
[0003] Despite more than fifty years of development, computer systems and computer programs remain difficult to use. In particular, individuals who are not well-versed in technology or computer programming encounter numerous problems in carrying out simple data processing tasks, such as collaborating on the form or content of a document, polling others to arrive at a decision, scheduling a meeting or activity, and other tasks. Several main approaches have been used in the past to facilitate these activities.
[0004] In a first approach, a pre-configured computer program or application is provided to all individuals who will participate in the data processing tasks. The individuals interact with the application to carry out the tasks. This approach requires little technical knowledge, but the approach is often too rigid and limits the individuals to using the particular forms, features and functions selected by the developers of the application. A related approach involves use of electronic mail ("e-mail") for distribution of information or for collaborative communications. E-mail is inefficient and often requires sending multiple messages before a task can be completed. Further, since the content of the messages is static, the content tends to become old and stale. The number and content of the messages are not easily organized.
[0005] In another prior approach, users construct their own custom computer program to perform exactly the desired task. This approach requires extensive technical knowledge that is beyond the capability of a typical user.
[0006] In a third approach, certain collaborative computing applications and environments have been provided. Applications such as Microsoft NetMeeting enable users to participate in online meetings, but have a significant limitation in that they are synchronous; a meeting participant must be online and present to participate. Applications such as Lotus Notes have enabled users to share documents, but creation and deployment of applications to carry out more sophisticated business tasks, such as automating personnel recruiting processes, is complicated and requires programming knowledge. Further, the collaborative processes that are supported by these applications "off the shelf" are limited and do not encompass many multi-step business processes.
[0007] A common disadvantage of all these approaches is that it is very hard for individual, non-technical users to create computer-based applications or systems that automate specific desired tasks and provide the applications or systems to others. Further, the approaches generally enable users to see only a static view of content that is under discussion or modification. Another disadvantage is that the approaches are typically synchronous; a user must be present during the collaboration and has no way to view actions or communications that have occurred before the user arrived or after the user leaves.
[0008] Another common disadvantage is that integrating the past approaches with existing or "legacy" databases and applications is extremely complicated, and requires programming knowledge. There is no easy way to enable such legacy systems to automatically interact with collaborative applications, without human intervention, to exchange data and carry out business processes. There is no simple means to enable the collaborative applications to receive signals from the external applications, take action based on the signals, or initiate new processes based on the signals.
[0009] Based on the foregoing, there is a clear need for an improved way to facilitate collaborative communication among individuals. In particular, there is a need for an approach that can enable new kinds of collaborative productivity applications, created by anyone and delivered using familiar communication mechanisms.
[0010] There is a related need for an approach that can facilitate distribution of secure, collaborative applications among separate but networked enterprises, so that users or applications of different enterprises can collaborate.
[0011] Computers have been used in messaging services since the 1960s, when suppliers of telex and telegraph services began deploying automated switching functions and providing complete computer-based messaging systems. An example of such a system is a teletypewriter system. Many of these systems used computers as data switches that relayed messages without providing message composition capabilities or the ability to search through previously sent messages.
[0012] Development of interactive time-sharing computer systems resulted in creation of linking tools that enabled two users to interlock their terminals in order to see what the other was typing. Mailbox tools were developed to allow users to send short messages to other users on-line on the same system. For example, the interactive time-sharing system at MIT's Project MAC had both linking and mailbox facilities that supported text messages.
[0013] Construction of the Advanced Research Projects Agency Network (ARPANET) in 1969-1975 initiated extensive research in store-and-forward communication techniques. An outgrowth of this research was the development of electronic messaging facilities, including electronic mail. Such facilities supported transport of simple text messages.
[0014] In the early 1980s, international standards bodies began work on electronic messaging with the goal of ensuring interoperability among different systems. In 1984, CCITT adopted a standard for store-and-forward messaging services called X.400 Message Handling Services (MHS). The International Standards Organization (ISO) created a competing standard called Message Oriented Text Interchange Standard (MOTIS). Differences among the versions were largely overcome by 1988.
[0015] The period 1973 to 1989 saw development of several computer systems that featured graphical user interfaces rather than character displays, such as the Xerox Alto, the Apple Lisa and Macintosh, and personal computers using Microsoft Windows. During this period, users developed interest in the ability to send messages having elements other than text. Examples of such multimedia e-mail systems include Slate, from BBN Software Products, and the first release of Lotus Notes, from Lotus Development Corporation.
[0016] To support transmission of formatted images, sound, files, folders, and video attachments, in 1992 the Internet Engineering Task Force (IETF) created a multi-media messaging standard known as Multipurpose Internet Mail Extensions (MIME). Using MIME, users of different kinds of computers can exchange e-mail messages that include formatted images, sound, files, folders, and video attachments. Further, a single MIME e-mail can contain alternative representations of the same data. For example, there can be an attachment in text form followed by one containing bitmap page images of the same information.
[0017] Implementations of MIME generally displayed messages in a graphical user interface window that presented different attachments as icons embedded within a text message. Other implementations, such as NeXTMail, from NeXT Computer, Inc., could display text, graphical elements, and attachment icons within the same message. A drawback of this implementation, however, was that to view different parts of a long message, a user was required to scroll down through a single contiguous message display in order to reach the desired part of the message.
[0018] Further, such systems provide no way to organize related elements of a message, other than manual cutting of one part of the message and pasting it into another upper or lower part of the same contiguous message. This procedure could quickly become unwieldy when such messages were exchanged among members of a group. As each member of the group added comments, graphics, or other attachments to the message, the message would become longer and longer, requiring extensive scrolling and searching to locate a desired part, or to correlate one comment of one user with a related comment of another user.
[0019] Other systems display multimedia attachments in a separate pane of a graphical user interface window that is displaying the message. For example, in Microsoft Outlook, when multimedia attachments are present, they are displayed at the bottom of the message window, divided from the message body by a separator bar. A disadvantage of this approach is that it is hard to correlate the attachment with a particular part of the message body.
[0020] In a more recent development, e-mail programs such as Microsoft Outlook have been linked to browser programs such as Microsoft Internet Explorer. Through such linkage, the e-mail program can receive an e-mail message formatted in Hypertext Markup Language (HTML) and display a rendered version of the HTML within an e-mail message display window. Using this approach, e-mail messages may contain text, graphics, and embedded hyperlinks to other content, multimedia resources, or applications. However, this approach has not cured the deficiency of prior approaches with respect to content organization and scrolling. It is still necessary to scroll through a long HTML e-mail to find desired content, and there is no simple way to correlate related content. Further, authoring HTML e-mail requires familiarity with complex HTML authoring software such as Microsoft FrontPage.
[0021] Based on the foregoing, there is a clear need in this field for a way to improve organization of content of e-mail messages.
[0022] There is a specific need for a way to organize related content portions of e-mail messages within the messages in a way that makes related content easy to find and display.
[0023] There is also a need for a way to create, deliver, receive, and display e-mail messages in which related content is correlated and accessed without scrolling or similar cumbersome operations.
[0024] E-mail, the World Wide Web, and instant messaging each have contributed to a revolution in the way people communicate. Each of these platforms offers a variety of benefits. For example, e-mail is available at the user's convenience; messages remain in an inbox until the user deletes them. Because e-mail arrives in the inbox, the user does not have to "go" anywhere to retrieve it. E-mail is useful for sending a note to a friend or addressing a large group. Because e-mail is individually addressable, a user can adapt the recipient list to the subject. Experts have estimated that users spend more time in e-mail than any other Internet application.
[0025] The World Wide Web ("Web") contains an abundance of information that is dynamically changing and ever growing. It is graphical and interactive, and offers the ability to conduct transactions. With relatively simple user interface operations, such as button clicks, the user can receive valuable information, purchase an item, or review work materials that have been placed on an internal website. Instant messaging offers the advantage of timeliness; the recipient knows that a newly received message is current, because the recipient is in a one-on-one communication session with the sender. This form of messaging has grown rapidly because people want information that is current.
[0026] However, e-mail, the web, and instant messaging have inherent limitations that restrict what users can do with them and how they communicate information to users. For example, e-mail today consists of static text that is neither dynamic nor interactive. E-mail messages are considered to be "dead on arrival" because they are current when sent, but are not current when read. For example, a user may not read an e-mail until hours after it was originally sent and there can be subsequent e-mails that supersede the original message, but the original outdated message remains in the inbox. There is no logical order to messages that are received in the inbox other than the time of arrival. Occasionally, the user can even receive an answer to a question before the question arrives, because of delays in server responses. The user is required to either scan all messages or sort them into some order to verify that the user has all needed information before taking action.
[0027] Unthreaded responses are another problem with e-mail. If a user sends a message to six people, and they all respond, the user receives six new messages in the inbox referring to one subject. The user is left to organize it all. Perhaps the most significant limitation of e-mail is the volume of messages that can flood a mailbox. When a user receives hundreds of e-mail messages a day, the sheer volume of e-mail is daunting.
[0028] Using the Web requires the user to proactively visit a location for information updates, and the user may need to visit multiple locations and pages before the user finds desired information. The Web is not personal or targeted, so it is not as effective as e-mail for communications. There are meeting sites on the Web, but users must seek out the destination, which requires them to remember URLs and passwords. There are also sites that offer group discussion and collaboration, but their groups are generally rigid and are based around a common interest.
[0029] Instant messaging allows for dynamic communication, but only if both participants are actively signed on and are available to receive messages. If one user is not able to respond, the link is dead and the user has lost the ability to instantly communicate. In addition, it's difficult to document "conversations" that occur through instant messaging; users lose the ability to have an audit trail or history.
[0030] Based on the foregoing, there is a need for a communication system that provides ways to share messages and information, ideally by providing the best features of e-mail, the Web, and instant messaging, while overcoming the limitations that each of these carries.
[0031] There is a particular need for methods and mechanisms for linking multiple messages together so that multiple message threads and sub-topics may be related and associated with a particular topic.
[0032] Users and applications may desire to link one message to another related message. However, past approaches to communication systems do not allow information, such as applications and electronic messages, to be related, threaded, managed and stored in an efficient, flexible, and simple way. Such approaches also do not provide a way to obtain a view of complex webs of messages.
[0033] There is also a need for methods and mechanisms that can aggregate related topical information within the context of a single message or web of messages.
SUMMARY OF THE INVENTION
[0034] The foregoing needs, and other needs that will become apparent from the following description, are achieved in the present invention, which comprises, in one aspect, a method and system for communicating and collaborating using transportable applications. Embodiments provide a breakthrough communication approach that improves collaboration among groups of individuals, within corporations, among customers, partners, and suppliers, and among distributed computer systems. In one approach, computer processes enable such users to create or host a new kind of collaborative productivity application called a transportable application. Transportable applications as disclosed herein may be used, for example, to bring together people, systems and information needed to contribute, make decisions, and take action on collaborative business processes or projects. In one embodiment, when a transportable application is opened, it reveals a live, shared, structured workspace that is specific to a project or process. Unlike past approaches, the workspace is continually updated to reflect the latest input of any recipient or user.
[0035] The transportable applications can be created by anyone, including individuals, non-technical users within an enterprise, or automatically by other computer programs, applications, or programmatic mechanisms. Each transportable application may comprise one or more pages each having one or more building blocks that encapsulate processing functions and data. Each building block may comprise one or more static content regions, one or more dynamic content regions, and other information. Content for the dynamic content regions may be stored in a database of a server.
[0036] The transportable applications can be distributed to others using existing transport mechanisms. For example, in one specific approach, transportable applications can be deployed in a manner analogous to sending an electronic mail message. Recipients may be individual users, groups, or other programs or applications.
[0037] The transportable applications can be accessed programmatically, or by an e-mail in-box, or using a web browser. When a transportable application is accessed by a recipient, data for its dynamic content regions is automatically retrieved. Input created by a recipient is accepted by the server and updates the dynamic content region of the transportable application. If a recipient modifies data in the transportable application, the modifications or updates are stored asynchronously and dynamically with respect to the sending and receiving of the modifications or updates by the recipients. Thus, the dynamic content is always current, and whenever any recipient opens and views the transportable application, the content of the transportable application is retrieved and displayed in then-current form.
[0038] Unlike past approaches, which rely on distribution of static information, transportable applications as defined herein enable full interaction and navigation of dynamic content without the user leaving the transportable application. A shared workspace is created in which multiple persons or systems can interact within the same transportable application, and all responses are aggregated in one place. The content of the transportable application is current when read; the transportable application is constantly updated so users can always see the most current information and responses of other group members. Transportable applications may be supported by related services, such as a secure mode that enables only authorized members to view and interact with the content, notifications that inform a user when an update to a transportable application has occurred, etc. Transportable applications may generate events that are acted upon by other transportable applications, and may act upon events that are received from external systems.
[0039] In a business enterprise environment, transportable applications and the systems and methods disclosed herein enable the enterprise to save time, reduce costs, and accomplish more. Companies can use transportable applications for simple shared projects to the complex and collaborative business processes required for global, multi-company projects, depending upon the need. Collaborative business processes may be rapidly automated and streamlined. Collaboration may be extended outside the corporate firewall by sending the transportable applications to others. The relevance and speed of collaborative application development may be improved. Costs of distributed team interaction may be reduced.
[0040] In one approach, the system features an integration framework comprising connectors that provide connectivity to and integrating with existing or "legacy" databases and applications. An author can create transportable applications that can retrieve data values from and set data values in such external applications and systems without programming knowledge, or even automatically from another program. As a result, legacy systems can automatically interact with collaborative applications, without human intervention, to exchange data and carry out business processes. A simple and efficient means is provided to enable the collaborative applications to receive signals from the external applications, take action based on the signals, or initiate new processes based on the signals.
[0041] According to another aspect, a method for associating related electronic messages in computer storage is disclosed. A first transportable application is created and stored. User input requesting creation of a link from the first transportable application to another transportable application is received. User input that selects a second transportable application from among a plurality of previously created transportable applications is received. A link from the first transportable application to the second transportable application is created and stored.
[0042] As a result, transportable application may be inter-related in complex message webs. The message webs may also be inter-related in message web rings. Links may be generated manually or automatically, based on context, workflow processes, or other known relationships among applications. Recipient lists and data may propagate among fields of linked transportable applications, directly or according to abstract business rules.
[0043] According to another aspect, a method for processing a request to display an electronic message is disclosed. First message data is generated. The first message data defines at least a first message portion and one or more navigation regions for one or more other message portions of a multiple-part electronic message having a plurality of message portions. The first message data is provided to a client. A request is received from the client for a second portion of the electronic message selected from among the other message portions. Second message data is generated which, when processed at a user interface of the client, causes the client to display the second portion of the electronic message. The second message data is provided to the client.
[0044] Multiple-part electronic messages are disclosed. A graphical user interface of an electronic messaging system displays a message in the form of one or more header portions and one or more body portions. Each of the body portions has a selection region. While one body portion is visible at a given time, all the selection regions are continuously visible in the user interface to facilitate selection of any of the body portions at a particular time. Selecting a selection region of a non-displayed body portion causes a server to generate a refreshed user interface that includes the entirety of the selected body portion, and that hides the previously viewed body portion. As a result, a large amount of associated information may be combined in a single message in a way that is clearly organized and easily accessible.
[0045] Transportable applications are disclosed. The transportable applications may be linked into webs of associated messages. For example, multiple related discussions or applications may be associated and organized. The webs of messages may be linked into rings of related message webs. As a result, workflow processes and complex associated information may be accessed and analyzed in an ordered way.
[0046] In other aspects, the invention encompasses computer readable media, and systems configured to carry out the foregoing steps. Other features and advantages of the invention will be apparent from the following detailed description, the drawings, and from the claims.
BRIEF DESCRIPTION OF THE DRAWINGS
[0047] The present invention is illustrated by way of example, and not by way of limitation, in the figures of the accompanying drawings and in which like reference numerals refer to similar elements and in which:
[0048] FIG. 1A is a block diagram providing a structural overview of a system context in which an embodiment may be used.
[0049] FIG. 1B is a block diagram that illustrates software elements of one embodiment of a service unit.
[0050] FIG. 1C is a block diagram of the system of FIG. 1A illustrating additional elements.
[0051] FIG. 1D is a block diagram illustrating an example of interaction of a container and its building blocks with system services.
[0052] FIG. 1E is a block diagram illustrating a high-level view of a process of creating and interacting with a transportable application.
[0053] FIG. 2A is a block diagram of system architecture that may be used to host the foregoing services and provide such services to clients.
[0054] FIG. 2B is a block diagram of an example software architecture of elements of the system of FIG. 2A.
[0055] FIG. 2C is a diagram of an example graphical appearance of a transportable application, according to one embodiment.
[0056] FIG. 2D is a block diagram of an alternate embodiment of a system architecture that features use of certain Microsoft.RTM. servers and systems.
[0057] FIG. 2E is a block diagram of an alternate embodiment of a system architecture that features use of certain Microsoft.RTM. servers and systems.
[0058] FIG. 2F is a block diagram of an alternate embodiment of a system architecture that features use of certain Microsoft.RTM. servers and systems.
[0059] FIG. 3 is a diagram of dependency relationships among interfaces that may be used, in one embodiment.
[0060] FIG. 4 is a block diagram of an example of a membership hierarchy.
[0061] FIG. 5 is a block diagram of objects and data communications paths involved in presentation of content associated with a building block.
[0062] FIG. 6 is a block diagram illustrating interaction of programmatic objects in one embodiment of a presentation model.
[0063] FIG. 7 is a flow diagram of one embodiment of a process of carrying out response-based notifications.
[0064] FIG. 8A is a diagram of an example graphical user interface screen display of the Escalation Exception Manager template.
[0065] FIG. 8B is a diagram of a screen display of an Addressing page that may be displayed, in one example embodiment.
[0066] FIG. 8C is a diagram of an example of the Message Security Options window that may be displayed, in one example embodiment.
[0067] FIG. 8D is a diagram of an example of the Page Security Options window that may be displayed, in one example embodiment.
[0068] FIG. 9A is a diagram of the Join Group screen that is displayed when the selected group is private.
[0069] FIG. 9B is a diagram of a My Groups screen that is generated and displayed when a user selects the My Groups link of the portal home page.
[0070] FIG. 9C is a diagram of a portion of the screen display of FIG. 9B.
[0071] FIG. 9D is a diagram of an Application Builder screen display that is displayed in response to selecting the Application Builder.
[0072] FIG. 9E is a diagram of a page navigation dialog that may be displayed, in one example embodiment.
[0073] FIG. 10A is a diagram of a Default Page Settings screen that may be used to change properties of a selected default page of a template.
[0074] FIG. 10B is a diagram of a Page Builder screen that may be displayed in response to selecting the Page Builder, in one example embodiment.
[0075] FIG. 10C is a diagram of a Survey Page Builder window that may be displayed, in one example embodiment.
[0076] FIG. 11A is a diagram of the graphical appearance of an Approval List building block as it appears in a transportable application page under development using the Page Builder.
[0077] FIG. 11B is a diagram of an example embodiment of a Discussion building block that may be used to captures a discussion between message participants.
[0078] FIG. 11C is a diagram of an example embodiment of a File Sharing building block, according to an example embodiment, which may be used to share an electronic file among a group of recipients for collaborative review or updating.
[0079] FIG. 11D is a diagram of an Image building block that may be provided, in one example embodiment.
[0080] FIG. 11E is a diagram of an Image Gallery building block that may be provided, in one example embodiment.
[0081] FIG. 11F is a diagram of an Information Fields building block that may be provided, in one example embodiment.
[0082] FIG. 11G is a diagram of an Inline Document building block that may be provided, in one example embodiment.
[0083] FIG. 11H is a diagram of an Inline Web Page building block that may be provided, in one example embodiment.
[0084] FIG. 12 is a diagram of an example transportable application that contains an inline Web page.
[0085] FIG. 13A is a diagram of an Invitation building block that may be provided, in one example embodiment.
[0086] FIG. 13B is a diagram of a Poll building block that may be provided, in one example embodiment.
[0087] FIG. 13C is a diagram of an Advanced Options window that may be displayed, in one example embodiment.
[0088] FIG. 13D is a diagram of a Schedule building block that may be provided, in one example embodiment.
[0089] FIG. 13E is a diagram of a Table building block that may be provided, in one example embodiment.
[0090] FIG. 14A is a diagram of a Choice building block that may be provided, in one example embodiment.
[0091] FIG. 14B is a diagram of a Free Text Response building block that may be provided, in one example embodiment.
[0092] FIG. 14C is a diagram of a Ratings building block that may be provided, in one example embodiment.
[0093] FIG. 15 is a block diagram that illustrates data and control flow among building blocks, data access objects, interface methods and the database.
[0094] FIG. 16 is a flow diagram illustrating a process of presenting building block information using the foregoing mechanisms.
[0095] FIG. 17 is a block diagram illustrating elements of an event handling system, in one example embodiment.
[0096] FIG. 18A is a block diagram of a first enterprise application integration approach that uses an asynchronous approach.
[0097] FIG. 18B is a block diagram of the system of FIG. 18A wherein a custom connector is used.
[0098] FIG. 18C is a block diagram of an application-server centric integration approach for providing a synchronous integration solution.
[0099] FIG. 18D is a block diagram of an enterprise application integration approach that provides synchronous integration through one or more synchronous protocols.
[0100] FIG. 18E is a block diagram of an enterprise application integration approach that uses event-based communication.
[0101] FIG. 19 is a block diagram that illustrates a computer system with which an embodiment may be implemented.
[0102] FIG. 20 is a block diagram illustrating a plurality of messages that are linked across different folders.
[0103] FIG. 21A is a diagram of a first embodiment of a graphical user interface display of a multiple-page electronic message.
[0104] FIG. 21B is a diagram of a second embodiment of a graphical user interface display of a multiple-page electronic message.
[0105] FIG. 22A is a diagram of a third embodiment of a graphical user interface display of a multiple-page electronic message.
[0106] FIG. 22B is a diagram of a fourth embodiment of a graphical user interface display of a multiple-page electronic message.
[0107] FIG. 22C is a diagram of a further embodiment of a graphical user interface display of a multiple-page electronic message that includes an indicator of additional pages.
[0108] FIG. 22D is a diagram of a further embodiment of a graphical user interface display of a multiple-page electronic message.
[0109] FIG. 23A is a flowchart of a process for linking messages, according to one embodiment.
[0110] FIG. 23B is a flowchart of a process of automatically linking messages in another embodiment.
[0111] FIG. 23C is a flow diagram of a process of automatically creating message links in response to a change in an object.
[0112] FIG. 23D is a flow diagram of a process of updating message links in response to changes in message content.
[0113] FIG. 23E is a flow diagram of a process of suggested message linking.
[0114] FIG. 24 is a flow diagram of a process of displaying HTML content in an e-mail client with browser navigation features.
[0115] FIG. 25A is a block diagram of a linked collection of related message webs, referred to herein as a message web ring.
[0116] FIG. 25B is a flow diagram of a process of creating a message web ring.
[0117] FIG. 26A is a block diagram illustrating messages in a message web having shared address lists.
[0118] FIG. 26B is a flow diagram of a process of generating a list of recipients of a transportable application.
[0119] FIG. 27A is a block diagram illustrating that the content of messages that are linked can be changed, with automatic propagation of changed content to linked messages.
[0120] FIG. 27B is a flow diagram of a process of updating data among linked messages in a message web.
[0121] FIG. 27C illustrates one application of the processes of FIG. 27A, FIG. 27B in which a linked collection of related messages are used to aggregate data from a child message up to a parent message.
[0122] FIG. 28A is a diagram of a graphical user interface display in which a transportable application includes a plurality of tabs that switch between the content of message web members.
[0123] FIG. 28B is a flow diagram of a process of adding tabs to a transportable application of the type shown in FIG. 28A.
[0124] FIG. 28C illustrates a notification message of a message web.
[0125] FIG. 29 illustrates a method for tracing deleted messages using links.
[0126] FIG. 30 illustrates a message web map that may be used in a graphical user interface of a messaging system that supports linked messages, in one example embodiment.
[0127] FIG. 31A, FIG. 31B, and FIG. 31C are diagrams of graphical user interface displays that illustrate an example of a recruiting process using a message web.
DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENT
[0128] In the following description, for the purposes of explanation, numerous specific details are set forth in order to provide a thorough understanding of the present invention. It will be apparent, however, to one skilled in the art that the present invention may be practiced without these specific details. In other instances, well-known structures and devices are shown in block diagram form in order to avoid unnecessarily obscuring the present invention.
[0129] Unless otherwise defined, all technical and scientific terms used herein have substantially the same meaning as commonly understood by one of ordinary skill in the art to which the invention pertains. ZAPLET is a trademark of Zaplet, Inc., Redwood Shores, Calif. Microsoft, Microsoft Outlook, Microsoft Active Directory, Microsoft Exchange Server, Microsoft SQL Server, Microsoft Internet Explorer, and Microsoft Internet Information Server are trademarks of Microsoft Corporation, Redmond, Wash. All other trademarks mentioned are the property of their respective owners.
[0130] Embodiments are described herein in sections according to the following outline:
[0131] 1.0 TRANSPORTABLE APPLICATION COMMUNICATIONS SYSTEM
[0132] 1.1 System Structural Overview
[0133] 1.1.1 Clients
[0134] 1.1.2 Networks
[0135] 1.1.3 Servers-Application Server, Proxy Server, Mail Server, Wireless Gateway, Directory Server, Middleware, File Server, Photo Server, Database Server, etc.
[0136] 1.1.4 Support Applications-Java, Database, etc.
[0137] 1.2 Transportable Applications-Structural and Functional Overview
[0138] 1.2.1 Graphical Appearance of a Transportable Application--Generally
[0139] 1.2.2 Receiving and Sending Transportable Applications
[0140] 1.2.3 Containers
[0141] 1.2.3.1 Root Container
[0142] 1.2.3.2 Contained Containers
[0143] 1.2.3.3 Implementation with Enterprise Java Beans
[0144] 1.2.4 Templates
[0145] 1.2.5 Pages and Building Blocks
[0146] 1.2.6 Object Model
[0147] 1.2.7 Membership
[0148] 1.2.8 Building Blocks--Programmatic Aspects
[0149] 1.2.9 Directory Integration--Global Object Identifiers
[0150] 1.3 Presentation of Transportable Applications
[0151] 1.3.1 E-mail Client Presentation
[0152] 1.3.2 Personal Portal Presentation
[0153] 1.3.3 Multiple-Page Transportable Applications
[0154] 1.3.4 Programmatic Processes for Presentation
[0155] 1.4 Authoring Transportable Applications
[0156] 1.4.1.1 Application Editor
[0157] 1.4.1.2 Page Editor
[0158] 1.4.1.3 Building Blocks--Examples
[0159] 1.4.1.4 Site Style Editor
[0160] 1.5 Communications From Transportable Applications to Users ("Notifications")
[0161] 1.5.1 Notifications Based on User Responses or Timed Events
[0162] 1.5.2 Notifications Based on Rules and Attributes
[0163] 1.6 Object Communications-Programmatic Methods
[0164] 1.7 Object Communications-Event-Driven Methods (Event Handling System)
[0165] 1.7.1 Database Schema
[0166] 1.7.2 Application Programming Interface & Object Methods
[0167] 1.8 Object Communications-External Systems
[0168] 1.8.1 Enterprise Application Integration Using Connectors
[0169] 1.9 Security Processes
[0170] 1.9.1 Cluster-Specific Encryption and Request Routing
[0171] 1.9.2 Sharing Transportable Application Data Among Multiple Sites
[0172] 1.10 System Administration Processes
[0173] 1.11 Using Transportable Applications in Business Processes and Workflow
[0174] 2.0 MULTIPLE-PART ELECTRONIC MESSAGES
[0175] 3.0 LINKING AND AGGREGATING MESSAGES
[0176] 4.0 HARDWARE OVERVIEW
[0177] 5.0 EXTENSIONS AND ALTERNATIVES
[0178] 1.0 Transportable Application Communications System
[0179] According to an embodiment, a communications system, and data processing methods that it carries out, facilitate collaborative communication and work among a group of individuals. Embodiments feature structures and processes for creating, authoring, transporting, updating, and viewing certain transportable applications. In general, a transportable application is an interactive, dynamic, addressable computer software application that can be transported among systems. A transportable application comprises one or more pages. Each page comprises one or more building blocks, and can be designed for either specific or general uses. Each building block contains the user interface, data elements, and processing capability that enable specific functions within a page.
[0180] A transportable application can be transported among different computer systems, clients and servers using transport mechanisms such as e-mail and other data transport protocols. When a transportable application arrives at a destination computer system, a user of that system can open the transportable application, view content that is dynamically asynchronously updated from a server source, and interact with functional elements of the transportable application in order to carry out work or other useful tasks.
[0181] Transportable applications are a new way to communicate by turning an existing transport mechanism, such as e-mail, into a live, shared place. Transportable applications enable users to share documents, data, business applications, schedules and other information with a group of people or with other systems. They can be used to make decisions with friends, family, or co-workers, schedule meetings and events, gather group data such as contact information, collect opinions, send invitations and RSVPs, and other tasks. In one embodiment, transportable applications enable all recipients in a group to communicate using just one e-mail message. Because a single transportable application takes the place of a thread of emails, transportable applications reduce inbox clutter and eliminate confusing strings of messages.
[0182] Transportable applications as described herein are better than e-mail because they provide information that is fresh and up-to-date. In one embodiment, transportable applications arrive in the user's inbox like normal e-mail, but they are current when the user opens them; new information can be included between the time the original author sent the transportable application and the time you open it. The transportable applications are current when read, not current when sent, eliminating the problem of receiving messages that are obsolete upon arrival.
[0183] The transportable applications add organization to the normally undifferentiated pile of individual e-mail messages. For example, transportable applications provide a structured container in which related data is collected, thus freeing users of organizing multiple pieces of e-mail. Additionally, transportable applications show aggregate views of multiple pieces of e-mail, thus summarizing information for better decision making. Also, transportable applications save time by reducing the volume of e-mail. By consolidating many responses into a transportable application, there are fewer pieces of e-mail to read.
[0184] Transportable applications are better than using the Web as a communications medium, for numerous reasons. For example, transportable applications push individualized messages into a user's Inbox. Transportable applications do not require a user to remember to visit a web site to see if they have a message.
[0185] Moreover, transportable applications are better than instant messaging as a day-to-day communications platform because transportable applications overcome the difficulty in getting multiple people to collaborate in real time. Transportable applications are targeted for group communication and persistent knowledge acquisition. In contrast, instant messaging is not designed for group communications and persistent knowledge acquisition.
[0186] 1.1 System Structural Overview
[0187] FIG. 1A is a block diagram providing a structural overview of a system context in which an embodiment may be used. In general, a client 102 is communicatively coupled through a network 108 to a service unit 105. The client 102 creates requests for transportable applications and dispatches the requests into network 108. The requests are received by service unit 105 and processed, resulting in creation of a response, which is sent back over network 108 to client 102.
[0188] Client 102 may be, for example, a workstation, personal computer, personal digital assistant, cellular telephone or other wireless processing device, or any other end station data processor. Client 102
also may be a programmatic process that forms a part of a larger computer system or application program. Network 108 is any data communication network that can carry data communications between client 102 and service unit 105. Network 108 may be a direct electronic connection of client 102
of service unit 105; a local area network; a wide area network; one or more internetworks; a combination of a an access network, a service provider network, and one or more internetworks; or any combination of the foregoing. Client 102 also may comprise the combination of any of the foregoing with a client software application that enables a user to view, create, edit, and manage transportable applications.
[0189] Service unit 105 is a facility that hosts hardware and software elements that provide the functions described herein, and may be a private business enterprise, a service provider that provides the functions described herein to others, e.g., on a licensed basis, subscription basis, etc., or any other entity that hosts appropriate service equipment and facilities.
[0190] Client 102 executes a browser 104 and a personal information manager 106. Browser 104 is a conventional Internet or World Wide Web browser, such as Microsoft Internet Explorer. Personal information manager 106 is one or more software elements that provide e-mail processing, among other functions. Optionally, personal information manager 106 also may provide other personal information management functions such as address book management, calendar management, notepads, task lists, etc. An example of a commercial product suitable for use as personal information manager 106 is Microsoft Outlook. In an alternative approach, client 102 may be an external computer system that receives transportable application programmatically, without using browser 104 or personal information manager 106.
[0191] FIG. 1B is a block diagram that illustrates software elements of one embodiment of service unit 105. In general, in one embodiment, service unit 105 hosts a multi-page messaging service 110 that is communicatively coupled to an event processor 112, HTTP service 114, message service 116, database service 118, security service 120, device gateways 122, and applications 124. Such elements inter-operate to provide multiple-page messages and carry out the processes that are described further herein.
[0192] FIG. 1C is a block diagram of the system of FIG. 1A illustrating additional elements.
[0193] In the example embodiment of FIG. 1B, multi-page messaging service 110 comprises component/container processing logic 130, administrative services 132, policy management & reporting services 134, access control service 136, mail services 138, device services 140, offline message processing services 144, and event and notification services 146.
[0194] The component/container processing logic 130 creates and manages a plurality of message components and message containers using processes that are described herein. The administrative services 132 provide administrative functions, such as adding or deleting users, importing files of users, identifying an external directory server and associating it with the system, etc. The policy management & reporting services 134
facilitate creating and managing policies for acting on transportable applications, access controls, etc.
[0195] Access control service 136 is communicatively coupled to security service 120, which may include an authentication, authorization and access (AAA) server, such as a RADIUS server. Access control service 136
communicates with other elements of multi-page messaging service 110 to receive requests to determine whether a particular user is authenticated in the system. The access control service also can receive and process requests to determine whether an authenticated user is authorized to access a particular message or a particular page of a particular message.
[0196] Security service 120 provides authentication and protection of user names and passwords. In one embodiment, security service 120 also provides Secure Sockets Layer (SSL) communication facilities so that communications from clients 102 to service unit 105, and from service unit 105 to an external directory server or other secure element, can be encrypted and carried out in a secure manner. Security service 120 also may provide means for integration with third-party security systems. Using such integration, security service 120 may be extended to provide authentication, access control, privacy, non-repudiation, and data integrity services. Such third-party systems may be the Sun Java Cryptography Engine, systems from Entrust, Cylink, Cybersafe, Verisign, etc. Security service 120 may support encrypted communications using asymmetric encryption algorithms such as RSA, DSS, D-H, etc.; symmetric encryption algorithms such as DES, triple-DES, DESX, IDEA, ES2, ES4, Blowfish, etc., message digest or hash algorithms such as SHA-1, SHA, MD5, MD2, RIPEMD, etc. Such encryption algorithms can be called programmatically from containers, building blocks, or system services that need to encrypt or decrypt data for communication, storage, or retrieval.
[0197] Mail services 138 is responsible for receiving data from other elements of the multi-page messaging service 110 and creating e-mail messages based on the received data. Mail services 138 also interfaces with message service 116 to dispatch and forward messages to users and clients. An example of a commercial product that may be used for message service 116 is Microsoft Exchange Server 2000.
[0198] In one specific embodiment, each of the foregoing services is implemented in the form of one or more Java class libraries. Thus, the services are provided by generic software modules that can be called by other software components of the system. The modules can incorporate third-party components, such as calculation engines, a workflow engine, etc.
[0199] FIG. 2A is a block diagram of system architecture that may be used to host the foregoing services and provide such services to clients.
[0200] One or more application servers 202 host containers in the form of Enterprise Java Beans 204 and store programmatic objects representing containers, building blocks, pages, and transportable applications in a cache 206. Application servers 202 execute code of the containers and building blocks and call servers and services in a services domain 201 to result in servicing client requests. In one embodiment, application servers 202 are implemented as a plurality of clusters of application servers, to provide load balancing and increased throughput. Inbound client requests are routed to a particular cluster using a routing mechanism that is described further herein.
[0201] Application servers 202 are communicatively coupled by link 210 to database server 208, which comprises one or more databases. The databases in database server 208 provide persistent storage of stored procedures, a repository of data and logic for containers, building blocks, and other system objects, and an event database that supports event-based messaging. Database 208 may be, for example, an Oracle database server, Microsoft SQL Server, etc. Link 210 may be implemented, in one specific embodiment, as JDBC calls from applications server 202 that traverse an SQL network using the SQLNet protocol and arrive at database server 208
in Oracle Command Interface (OCI) format. Alternatively, ODBC may be used, as in the case of SQL Server.
[0202] The database server 208 provides one source for content for building blocks and containers that application servers 202 may dynamically retrieve and present to clients 102 as part of processing transportable application and executing their building blocks. Other data sources may be used. In one embodiment, application servers 202 are communicatively coupled by an NFS link 246 to one or more file servers 244. This arrangement enables application servers 202 to obtain text files, word processing documents and other contents of a file system to include in the dynamic content of a building block or for other purposes.
[0203] One or more adapters 209 cooperate with a connection framework in application server 202 to communicate with one or more external systems or applications 205. Such external systems or applications include legacy applications, enterprise systems, etc., as described further herein.
[0204] In another embodiment, application servers 202 are communicatively coupled to one or more image servers 240 by an HTTP link 242. This arrangement enables application servers 202 to rapidly retrieve one or more graphical images, digital photos, and other image information to include in transportable applications when they are presented to clients.
[0205] Application servers 202 may obtain dynamic content from one or more external sources and may communicate with clients using connections to public networks. In one embodiment, application servers 202 are communicatively coupled by a first HTTP link 236 to an HTTP server 232
(Web server 232), proxy server 234, and second HTTP link 238. This arrangement enables application servers 202 to receive a large number of separate HTTP connections and requests from clients 102 over second HTTP link 238, which are received at proxy server 234 and passed to the application servers over the first HTTP link 236. When the application servers have prepared content for presentation to clients in response to client requests, Java Server Pages elements of the application servers send the content to HTTP server 232 over the first HTTP link 236. The HTTP server 232 then issues an appropriately encapsulated HTTP response to the clients over HTTP link 238, through proxy server 234.
[0206] Application servers 202 are also communicatively coupled by link 214 to middleware 212, which provides basic messaging infrastructure functions. In one specific embodiment, link 214 uses the Java Messaging System (JMS) protocol, which may also be used to transport data on link 215 from middleware 212 to one or more event daemons 216 of event service 146. The event service 146 is communicatively coupled by link 218 to database server 208. In one specific embodiment, link 218 is implemented by JDBC calls from event service 146 that traverse the SQLNet and arrive at database server 208 in OCI format.
[0207] Directory information such as user names and group membership may be obtained from one or more directory servers 220 that are communicatively coupled to application servers 202 by link 224 and to event service 146 by link 222. In one embodiment, directory servers 220
conform to Lightweight Directory Access Protocol (LDAP) and communications on links 222, 224 are carried out using LDAP. Directory servers 220 need not be co-located with application server 202, and may be located in any location that is accessible using LDAP communications over a network or similar facility.
[0208] Application servers 202 communicate with e-mail clients using mail servers 228, and with wireless devices, such as wireless personal digital assistants and cellular phones, using a wireless gateway 226. In one embodiment, one or more mail servers 228 are communicatively coupled by an SMTP link 225 to event services 146, which is responsible to generate events that request mail transport. Event services 146 also are coupled by SMTP link 225 to wireless gateway 226, and the wireless gateway may be communicatively coupled to the mail servers by link 227. Mail servers 228
and wireless gateway 226 communicate with e-mail clients, other client devices using external networks that are reached using SMTP link 230.
[0209] FIG. 2B is a block diagram of an example software architecture of elements of the system of FIG. 2A.
[0210] The software elements of the system may be viewed as logically organized in a client tier 248, middle tier 252, and data tier 275. Client tier 248 comprises an e-mail client 249 that executes on a client computer, e.g., client 102, and a browser 250 that executes at the same client. The e-mail client 249 and browser 250 may interoperate with a shared DLL that provides HTML parsing functions, so that the e-mail client can display HTML e-mail messages.
[0211] In one embodiment, system services generally are provided by a plurality of servlet constructs that implement the services. For example, middle tier 252 comprises a mail server 254 that communicates with e-mail client 249 over a network link. The mail server is communicatively coupled to one or more mail queuing servlets 262 that are organized in a Web container 258 of program elements. The Web container 258 further comprises a mail formatter 260, which may be implemented in the form of one or more Java Server Pages. Creation and modification of dynamic content of a transportable application is generally performed by dynamic content creation servlets 264. A Web page formatter 266, implemented in the form of one or more JSPs, is responsible for formatting Web pages or other HTML content that may form a part of a transportable application.
[0212] In one specific embodiment, middle tier 252 further comprises an EJB container 268 that comprises a plurality of program elements in the form of Enterprise Java Beans (EJBs). EJBs are Java.RTM. language classes that can interoperate with a plurality of servers within an enterprise network. Data access EJBs 270 are responsible for interfacing higher-layer elements with database 208 and one or more stored procedures 276 in the database. Core EJBs 272 are responsible for carrying out access control processes, managing event services, etc. Data and event integration EJBs 274 provide an interface to external systems such as a legacy database 278, an enterprise application integration program or bus 279, etc.
[0213] In an embodiment, these elements are implemented using Java-based technologies in conformance with the Java 2 Enterprise Edition (J2EE) specification for server-based applications. However, embodiments are not limited to this context.
[0214] FIG. 2D is a block diagram of an alternate embodiment of a system architecture that features use of certain Microsoft.RTM. servers and systems. In general, FIG. 2D depicts a client layer 2000 that communicate with servers 2002. Client layer 2000 comprises, in this example, a Microsoft Outlook client 2004. Servers 2002 comprise a Microsoft Exchange server 2008, an Active Directory server 2026, Web storage system 2020, application server 202, database server 208, and host integration server 2034.
[0215] In this configuration, Outlook client 2004 communicates over a mail application programming interface (MAPI) or remote procedure call (RPC) link 2006 with a MAPI processor 2012 of the Microsoft Exchange server 2008. The Microsoft Exchange server 2008 further comprises an SMTP agent 2010, OWA agent 2014, event handling system 2016, and Exchange OLE Database agent 2018. The SMTP agent 2010 can communicate with SMTP-compatible mail servers to enable the system to transport e-mail messages across a network. Event handling system 2016 receives events generated by application server 202 or its applications and processes them by, for example, storing information in mailbox store 2022 and public stores 2024 of Web storage system 2020. Database operations by or on behalf of application server 202 are facilitated by Exchange OLE Database agent 2018, which is communicatively coupled to Web storage system 2020.
[0216] Web storage system 2020 provides Exchange server 2008 with a unified storage name space for all messages, calendar information, documents, discussions, or other data. Its objects are accessible using HTTP, XML, COM, WebDAV, and file system calls. In one embodiment, transportable applications are stored in Web storage system 2020. Such transportable applications, their document attachments, and their building blocks are addressable in Web storage system 2020 using URLs. Web storage system 2020 may also store information about a plurality of Exchange offline folders, facilitating synchronization of offline updates to transportable applications.
[0217] Active Directory server 2026 is communicatively coupled to Exchange server 2008 and stores directory information, such as definitions of users and groups, locations of network elements such as servers, hosts, workstations, and printers, etc. The Active Directory server 2026 is also accessible by application code 202A, which is hosted by application server 202, through a common data object (CDO) agent 2028 that is hosted by the application server. Active Directory is an example of an LDAP directory as described herein.
[0218] Application server 202 further comprises an Active Data Objects (ADO) process 2030 that is communicatively coupled to Exchange OLE Database agent 2018 and to database 208 and host integration server 2034. These communication paths enable functions of application code 202 to set and retrieve values of data objects that are stored in database 208, in external legacy systems that are accessed using host integration server 2034. Further, the application code 202 can set and retrieve values of data objects that are stored in Web storage system 2020 by appropriate messages to Exchange OLE Database agent 2018.
[0219] Application code 202A of application server 202 comprises sequences of computer program instructions that are configured to carry out the functions that are described herein.
[0220] In the configuration of FIG. 2D, transportable applications that are hosted by application server 202 may be created, viewed, and managed using Outlook client 2004. The Outlook client 2004 is an example of an HTML e-mail client that can display transportable application content in rich HTML form within an e-mail message window. The transportable applications may be transported over a network using Exchange server is 2008. Active Directory server 2026 may serve as a source for user and group information. Building blocks may be implemented in the form of Web forms, which provide user interface front-ends to data and logic in the Web storage system 2020.
[0221] Exchange server 2008 includes instant messaging support with presence detection API's. Thus, application server 202 may determine, by an appropriate API call, if participants in transportable applications are actually online, and utilize instant messaging for communications, and record such sessions at user request. Transportable applications can include NetMeeting features for initiating and storing data conferences, such as virtual white board, application sharing, video conferences, audio conferences, etc., through Exchange server 2008.
[0222] Exchange has threaded discussion capabilities that are programmatically available. In one embodiment, application server 202
uses the threaded discussion APIs to provide a threaded discussion capability, with presence detection, as a core building block.
[0223] Calendaring and contact information access through Exchange server 2008 allows for scheduling features, such as automatic meeting creation, available time lookup and resolution, meeting cancellations, etc., and more integrated addressing and address validation on the server side. Use of Exchange server 2008 also enables application server 202 to communicate transportable applications to PDA, mobile phone, and other non-PC devices, over wired and wireless.
[0224] A workflow engine of Exchange server 2008 has an accompanying graphical workflow designer that allows execution of logic and invocation of components in and outside of Exchange, via COM, that provide message routing, approval, and state transitions. Thus, transportable applications of application server 202 may participate and drive these workflows.
[0225] FIG. 2E is a block diagram of an alternate embodiment of a system architecture that features use of certain Microsoft.RTM. servers and systems. As in FIG. 2D, the architecture of FIG. 2E features an Outlook client 2004, Exchange server 2008, Active Directory server 2026, Web storage system 2020, application server 202, and host integration server 2034. The architecture of FIG. 2E further features an Internet Information Server (IIS) 2036 that is communicatively coupled to Exchange server 2008 via OWA agent 2014. In client layer 2000, an Internet Explorer browser 2005 is communicatively coupled, for example, over a network, to IIS 2036.
[0226] Browser 2005 and Outlook client 2004 may carry out HTML display functions using a shared DLL.
[0227] In this configuration, application server 202 may serve transportable applications to a user through browser 2005, Outlook client 2004, or both. For example, a user may use browser 2005 to open an HTTP connection to IIS 2036, which communicates HTTP requests and posts among application server 202 and the browser. Using this mechanism, a user may obtain the portal presentation described herein and may view, create, and manage transportable applications. Alternatively, as in FIG. 2D, the user may obtain a portal view, or view an individual transportable application, in an e-mail window that is generated by Outlook client 2004.
[0228] FIG. 2F is a block diagram of an alternate embodiment of a system architecture that features use of certain Microsoft.RTM. servers and systems. As in FIG. 2E, the architecture of FIG. 2F features an Outlook client 2004, Exchange server 2008, Active Directory server 2026, Web storage system 2020, application server 202, host integration server 2034, and an Internet Information Server (IIS) 2036 that is communicatively coupled to Exchange server 2008 via OWA agent 2014. In client layer 2000, an Internet Explorer browser 2005 is communicatively coupled, for example, over a network, to IIS 2036. Any other browser 2005A, such as Netscape Navigator, may participate in client layer 2000. Browser 2005 and Outlook client 2004 may carry out HTML display functions using a shared DLL.
[0229] The architecture of FIG. 2F further features a plurality of Active Server Page (ASP) constructs that are hosted by IIS 2036. The ASPs are callable from application code 202A, as indicated by link 2038, by passing URLs over a network to IIS 236. The URLs identify a particular ASP and provide one or more function parameters or data values.
[0230] In this configuration, certain transportable application functions that are defined herein are carried out by appropriately configured ASPs 2040 rather than by application code 202A. For example, any of the functions that are described herein as implemented using JSP constructs may be implemented, alternatively, using ASPs 2040 in a system configured as in FIG. 2F.
[0231] In still another alternative configuration, elements of the Microsoft ".NET" infrastructure are used. In this embodiment, the database server 208 is Microsoft SQL Server, but all other components are found within Windows 2000, Windows XP, and related server products of Microsoft. For example, ISAPI filters are used as a substitute for J2EE servlets as disclosed herein; Active Server Pages substitute for JSP's; Microsoft Message Queues (MSMQ) substitute for JMS; COM+ components substitute for EJB's; and ODBC is the database communication protocol rather than JDBC. Data access objects (DAOs) as disclosed herein may be implemented using a custom OLE database provider that is compatible with the Microsoft Active Data Object (ADO+) framework. COM+ access to external legacy applications may be provided as an alternative to JCA or connectors as disclosed herein.
[0232] As set forth in the foregoing, embodiments of transportable applications, an application server, and associated functions described herein are applicable equally to contexts that use Microsoft servers, products, and related elements, as well as Java servers, open-source elements, servers or products of Sun Microsystems and its partners, etc.
[0233] 1.2 Transportable Application--Structural Overview
[0234] A system having the foregoing configuration may be used to create, send, respond to, interact with, and manage a plurality of transportable applications.
[0235] FIG. 1E is a block diagram illustrating a high-level view of a process of creating and interacting with a transportable application. In block 190, an author of a transportable application accesses an application authoring system. The application authoring system may comprise a transportable application editor that is provided by application server 200 and accessed through an enterprise network or over a public internetwork.
[0236] In block 191, the author creates, authors and edits a new transportable application using the editor, resulting in creating and storing the transportable application, as shown in block 192. Such authoring also includes identifying one or more recipients of the transportable application. In block 193, the transportable application is transported to all the recipients using a suitable transport mechanism. Transport mechanisms may include e-mail, wireless gateways, or other means.
[0237] When the transport mechanism is e-mail, in block 194, each recipient receives an e-mail message identifying the transportable application and appearing to contain the transportable application. Assume that a particular recipient opens the e-mail message that identifies the transportable application. In response, in block 195, the system dynamically determines what client e-mail program is in use, and determines what display capabilities it has with respect to fonts, colors, graphics, other types of information, etc. In block 196, the transportable application is displayed to the user using its e-mail client, based on the available display capabilities of the client. Further, any dynamic content associated with the transportable application is automatically retrieved, in its then-current form, from a database and displayed as part of the transportable application.
[0238] In block 197, the recipient responds to the transportable application in a manner analogous to replying to an e-mail message. Text comments or other changes to dynamic content of the transportable application may be entered in the application as it is displayed within a window of the e-mail program. Any such changes are updated at the database in dynamic content associated with the transportable application, as shown by block 198. As a result, any other recipient who subsequently views the same transportable application will receive a current view of the dynamic content. In this sense, the dynamic content and the transportable application is always current when read.
[0239] FIG. 1F is a block diagram illustrating details of a process of authoring a transportable application as in block 191 of FIG. 1E.
[0240] In block 191A, one or more pages for the transportable application are created or retrieved from storage. In block 191B, a template for the transportable application is created. In block 191C, a transportable application is created based on the template and/or the pages.
[0241] Each of blocks 191A, 191B, 191C may be carried out by a different individual. For example, one person can create a template and another person can created a transportable application based on the template. Recipients of the transportable application may, depending on the settings of the transportable application, change the structure of the transportable application. Alternatively, the same person can be responsible for all stages of the authoring process by creating templates, authoring new transportable applications, and participating in collaboration with others within the framework of a transportable application. Individual pages and templates may be shared with others.
[0242] 1.2.1 Graphical Appearance of a Transportable Application--Generally
[0243] FIG. 2C is a diagram of an example graphical appearance of a transportable application, according to one embodiment. In this embodiment, a transportable application is displayed in a transportable application window 280 that comprises, in general, a command options bar 282, an action request or note 284, a header bar 286, and one or more pages 287A, 287B. Each of the pages 287A, 287B may comprise one or more building blocks 292, 294. Each building block contains the user interface, data elements, and processing capability that enable specific functions within a page. Navigation among pages is accomplished by selecting a navigation area 288 associated with a particular page, or by selecting a navigation direction icon 296.
[0244] In one specific embodiment, command options bar 282 includes a New Message button, Reply to Author button, Forward button, and Print View button. The New Message button is used to author a new transportable application message. A Reply to Author button is used to send a message directly to the author of the transportable application displayed in window 280. The Forward button is used to forward the transportable application to additional recipients. The Print View button is used to obtain a properly formatted printed version of the transportable application.
[0245] Header bar 286 provides addressing information identifying the author of the transportable application, its recipients, and its subject or title. In one embodiment, the specific names of recipients are hidden, and header bar 286 includes a View All Recipients link 286a. Selecting the View All Recipients link 286a causes the system to display a list of all recipients.
[0246] One or more notifications may be associated with a transportable application. If a notification is present for a transportable application, a notification link 290 is displayed, and provides a hyperlink with which the user may obtain a view of the notifications. When a user receives a transportable application, a notification system enables the user to "opt-in" to individual transportable applications in which the user has an interest. In one approach, if dynamic content associated with the transportable application changes, a new copy of the transportable application is sent to the user. Alternatively, notifications may comprise re-bolding an identifier of the transportable application in the user's e-mail client. In this manner, the user can track changes without having to remember to continually go back and check on the state of the transportable application. For example, a user may read a transportable application, opt-in to the notification system for that transportable application, delete the transportable application from the user's e-mail Inbox, and wait for a notification when anything changes in the transportable application.
[0247] Each user is sent only a single copy of the transportable application, even if there are multiple responses to it. The system knows when the transportable application has been read by the user and can minimize the number of notifications sent. If the user has not opted-in to the notification system, the user can always open the transportable application or refresh the display of client 102, e.g., by selecting a Refresh button of the browser, to see the latest information.
[0248] A transportable application also can change state during its lifetime. For example, an author can close a transportable application; this notifies the recipients that comments or replies are no longer being accepted on the subject of the transportable application. The author of the transportable application can then communicate a decision or the results of the transportable application to all the recipients. Thus, the user no longer needs to spend time writing a response to an e-mail when its subject matter is essentially closed.
[0249] An Options link 291 provides a mechanism to display a list of actions that the user can take with the transportable application.
[0250] The action request or note 284 displays a brief urgent note or request from the author of the transportable application. Such notes provide a way to carry out a side conversation among recipients of the transportable application and the author or other recipients. Such notes may be stored persistently and generally are directed to one recipient. In one embodiment, a transportable application that is sent in the form of an HTML e-mail to a recipient may comprise a script, which is executed when the message is opened by the recipient, that establishes an HTTP connection to application server 202, requests any changes to dynamic content of the transportable application, determines whether the recipient has received any notes, and displays the notes if any have been received. The notes may be displayed within the transportable application, as in FIG. 2C, or in a pop-up window that is displayed separately.
[0251] 1.2.2 Receiving and Sending Transportable Applications
[0252] In general, interacting with a transportable application involves receiving a message that references or contains a transportable application, entering a response, and using one or more transportable application commands. A user may receive a transportable application as a message carried using any suitable transport mechanism. In this description, for purposes of illustrating a simple example, the transport mechanism is assumed to be e-mail. However, any other suitable transport mechanism may be used, such as wireless gateways, voice and other multimedia protocols, etc. Further, various e-mail protocols may be used, such as SMTP, MAPI, etc.
[0253] When a user receives a transportable application, the user receives a specially designated e-mail message in the in-box of the e-mail client of the user. To begin interacting with the transportable application, the user opens the message. In response, the contents of the transportable application are automatically dynamically updated from a server, such as application server 202 of FIG. 2A. The transportable application is also updated when a user submits a response.
[0254] Specific processes for interaction with a transportable application depend on what pages and building blocks are contained in the transportable application. Specific building blocks are described further herein. In general, interaction involves selecting a desired page using a navigation area 287B and locating a response button. Each building block has a response button such as "Enter Response," "Add Image," "Add Table Row," etc. The response button is selected. In response, the system generates and sends an Enter Response window to the client 102, which displays it as a new graphical user interface window. An appropriate response is entered.
[0255] When the response is complete, the user selects a Submit button to send the response information to the server. Alternatively, the user may select Cancel to exit without entering a response. In response to a Submit selection, information for the transportable application in a database associated with the server is updated to show the response. The foregoing steps may be repeated any number of times for any number of pages in the transportable application. When the user is finished entering responses, the user closes the message.
[0256] As noted above, notifications may be turned on and off by selecting notifications link 290. FIG. 7A is a diagram of a Set Notifications user interface window that is displayed when notifications link 290 is selected. Window 700 comprises an On radio button 702, Off radio button 704, and Customize radio button 706.
[0257] If the Customize radio button 706 is selected, in response, the server generates and sends to the client a Customize Notifications window. FIG. 7B is a diagram of a Customize Notifications window that may be displayed. The Customize Notifications window 708 displays one or more page check boxes 710 corresponding to pages of the transportable application. Selecting one of the check boxes 710 causes the system to generate a notification message only when a change occurs in the associated page. Window 708 also comprises an Overall Application check box 712 that triggers a notification when any change occurs in any part of the transportable application. Window 708 further comprises a Page Change checkbox 714 that triggers a notification when one or more pages are added to the transportable application or when its status changes. Window 708 also comprises a Set Frequency pull-down menu 716 that enables change notification messages to be sent at particular time intervals.
[0258] 1.2.3 Containers
[0259] Each transportable application comprises one or more containers. Each container is implemented in the form of a programmatic object in an object-oriented programming environment. Each container may be a root container or an embedded container. Each transportable application has one root container, and one or more embedded containers.
[0260] The root container is responsible for interacting with transport services such as mail services 338, access and addressing services, and sending only new or changed information to and from its contained building blocks. Each root container stores a list of pointers or other references to contained child objects or building blocks. Thus, a tree walk of the pointers may be carried out to identify all building blocks or other child nodes of a particular container. A child, such as a building block or contained container, may have multiple parent containers; this mechanism enables, for example, a particular page to appear in more than one transportable application or in more than one template.
[0261] Each embedded container references and logically contains one or more other embedded containers or building blocks. Containers can call functions of the system services shown in FIG. 1A, FIG. 1B, and FIG. 1C, and there