US20180075093A1 - Sharing document links from multiple data providers - Google Patents

Abstract

A document sharing system includes a plurality of different data provider implementations. The document sharing system exposes a common application programming interface to a plurality of different clients and receives data requests identifying a given data provider, from the clients. The document sharing system then uses the data provider implementation for the data provider identified in the request, in order to obtain the requested data, and place it in a common data structure that is returned to the client.

Description

CROSS-REFERENCE TO RELATED APPLICATION
• The present application is a continuation of and claims priority of U.S. patent application Ser. No. 14/087,491, filed Nov. 22, 2013, the content of which is hereby incorporated by reference in its entirety.
BACKGROUND
• A variety of different types of messaging systems are currently in wide use. Some such messaging systems include, for instance, electronic mail (e-mail) systems, instant messaging systems, communication systems within social networking systems, among others.
• In such messaging systems, it is common for users to send attachments (or links to attachments) to one another. In social network systems, users can make attachments or objects available to one another in various groups. The attachments are often provided as a link to an object, such as a document, a picture, a directory, a folder, etc. The objects are stored at a given location. Because a wide variety of different users tend to send one another a wide variety of different types of attachments, the attachments can be located in a wide variety of different locations, and they can be provided by a variety of different data providers.
• This can present some challenges. For instance, different data providers often provide data in different structures, formats, or according to different schemas. For a given client to obtain access to data from multiple different providers, the client normally downloads a separate client application for each provider. When the client wishes to obtain data from a given provider, it uses the client application associated with that provider.
• The discussion above is merely provided for general background information and is not intended to be used as an aid in determining the scope of the claimed subject matter.
SUMMARY
• A document sharing system includes a plurality of different data provider implementations. The document sharing system exposes a common application programming interface to a plurality of different clients and receives data requests identifying a given data provider, from the clients. The document sharing system then uses the data provider implementation for the data provider identified in the request, in order to obtain the requested data, and place it in a common data structure that is returned to the client.
• This Summary is provided to introduce a selection of concepts in a simplified form that are further described below in the Detailed Description. This Summary is not intended to identify key features or essential features of the claimed subject matter, nor is it intended to be used as an aid in determining the scope of the claimed subject matter. The claimed subject matter is not limited to implementations that solve any or all disadvantages noted in the background.
BRIEF DESCRIPTION OF THE DRAWINGS
• FIG. 1 is a block diagram of one illustrative document sharing architecture.
• FIG. 2 is a flow diagram illustrating one embodiment of the operation of the document sharing architecture shown inFIG. 1.
• FIG. 3A is a diagram of one illustrative attachment data provider base class.
• FIG. 3B is a diagram of one illustrative implementation of the base class shown inFIG. 3A, for a given data provider.
• FIG. 4 is a block diagram of the architecture shown inFIG. 1, deployed in a cloud computing architecture.
• FIGS. 5-9 show various embodiments of mobile devices.
• FIG. 10 is a block diagram of one illustrative computing environment.
DETAILED DESCRIPTION
• FIG. 1 is a block diagram of one illustrativedocument sharing architecture100.Architecture100 illustratively includes a messaging server (such as an electronic mail server)102 that interacts with a plurality of different data providers104-106. It will be appreciated that data providers104-106 can be cloud-based data providers or other hosted data providers, or they can be local to mailserver102. A number of these different architectures are described below with respect toFIG. 4. Suffice it to say, for now, thatmail server102 illustratively receives data requests from auser108 through aclient device110, for information stored on one of data providers104-106.Mail server102 accesses the appropriate data provider and provides the requested data back toclient device110 for display touser108.
• In the embodiment shown inFIG. 1,mail server102 includesprocessor112, data store113 (with cache115) anddocument sharing system114.Document sharing system114 illustratively includesdata parsing component116, commondata model component118, dataprovider identification component120,client communication component122 and a plurality of data provider implementations124-126. Each data provider implementation124-126 (which can be written by a third party to implement a defined interface) exposes a corresponding application programming interface128-130, respectively. The data providers104-106 illustratively includecorresponding data stores132 and134, respectively. The information stored indata stores132 and134 is illustratively served by a server or other processor in data providers104-106, respectively. Data providers104-106 illustratively communicate withdocument sharing system114 andmail server102 over their corresponding application programming interfaces128-130 exposed by their corresponding implementations124-126, respectively.
• Client communication component122 inmail server102 illustratively exposes a client application programming interface (API)136.Client110 communicates withmail server102 overclient API136.
• In the embodiment shown inFIG. 1,client device110 illustratively includesprocessor138,data store140 and one ormore client applications142.Client applications142 illustratively include a communication application (such as an e-mail application) that generates user interface displays144 with user input mechanisms that allowuser108 to interact withmail server102, such as to send and receive messages that can include attachments.
• Before describing the operation of mail server102 (and specifically document sharing system114) in more detail, a brief overview will be provided to enhance understanding. It is first assumed thatuser108 logs into the e-mail system implemented bymail server102, and requests data from one of the data providers104-106 (such as attaching an attachment to a message or retrieving an attachment from a message). This request is sent using the commonapplication programming interface136 exposed byclient communication component102, which handles client communication with client devices (such as device110). The request for data illustratively identifies a specific data provider so thatdocument sharing system114 illustratively uses the proper data provider implementation124-126 to communicate with the identified data provider over the corresponding application programming interface128-130. The requested data is received from the corresponding data provider and parsed byparsing component116 into a common data structure represented by commondata model component118. The common data structure presents data from a plurality of different data providers104-106 according to a common structure (that is the same, regardless of the data provider) that can be viewed byuser108 usingclient device110. A more detailed description of the operation ofarchitecture100 will now be provided.
• FIG. 2 is a flow diagram illustrating one embodiment of the operation ofarchitecture100 in more detail.FIGS. 1 and 2 will now be described in conjunction with one another.
• It is first assumed thatuser108 wishes to obtain information from a data provider (such as by attaching an attachment to a message, opening an attachment in a message or otherwise). It is also assumed that data providers104-106 illustratively store data, and provide it in response to requests, using their own formats, protocols, schemas, or at least different data structures, which may be different from one another. In one embodiment, however, commondata model component118 obtains data that is parsed bydata parsing component116, from the various data providers, and represents it to user108 (through client device110) in a common way, regardless of the specific data provider that provides the data.
• At some point, then,user108 interacts with user interface displays144 to request access to data from a specific data provider.Client communication component122 receives this request via API136 fromclient device110. Receiving the client request for data is indicated byblock150 in the flow diagram ofFIG. 2. Receiving it over the client API is indicated byblock152. The request can includeauthentication information154, such as log-in information that allowsclient108 to log intoe-mail server102. It also illustratively includes adata provider identifier156. This uniquely identifies the specific data provider104-106 from which the data is being requested. The data request also illustratively includes an identity of the requesteddata158. Of course, the request can includeother information160 as well.
• The data request provided usingAPI136 is then passed to dataprovider identification component120 which identifies the particular data provider104-106 from which the data is being requested. Identifying the data provider in the request is indicated byblock162 inFIG. 2.
• Document sharing system114 then uses the particular data provider implementation124-126 to interact with the identified data provider104-106. For the sake of the present discussion, it is assumed that the data request passed in usingAPI136 byclient device110 has identifieddata provider104 as the particular data provider from which data is being requested. The data request can be a wide variety of different types of requests, such as to obtain file/folder information, to download or upload files, or to update file permissions. Thedata provider implementation124 exposes a provider-specific API128 which can be used to make calls todata provider104 and to receive information fromdata provider104. Assuming, for instance, that the data request was to view specific folder or file information (so the user can, for example, attach an object to an electronic mail message or make it available to a group in a social network or otherwise),data provider implementation124 thus makes the web service calls overAPI128 todata provider104 in order to retrieve the folder and file metadata that makes up the document library indata store132. Accessing the data provider implementation for the identified data provider and making the service calls using that implementation are indicated byblocks164 and166 in the flow diagram ofFIG. 2, respectively. The service calls illustratively identify the particular user, as indicated byblock168, and identify the requested data as indicated byblock170. The service calls can includeother information172 as well.
• In any case,data provider implementation124 receives the requested information overAPI128 fromdata provider104. This is indicated byblock174. The data can be received from the different data providers in a wide variety of different ways. For instance, some data providers provide the data as aserialization176. It can be received in other ways as well, such as inXML178, or in other ways that are specific to the given data provider from which the information is received. This is indicated byblock180.
• The received data is then provided todata parsing component116 where it is parsed. This is indicated byblock182. The particular way that the data is parsed will depend on the particular data provider that it was received from. For instance,data parsing component116 can apply various parsing rules, based upon the particular data provider providing the data, and based upon the particular provider-specific way that the data is provided. By way of example, if two different data providers provide requested data as a serialized output, the items in the serialization may be in different order. They may also be named using different naming conventions. Therefore, the requested data is parsed into the desired parts (that will eventually be presented to the user) bydata parsing component116. Parsing the order of serialization is indicated byblock184 in the flow diagram ofFIG. 2. Parsing the actual items in the serialization is indicated byblock186. Parsing according to naming convention is indicated byblock188. These are all exemplary only. Also, in one embodiment, some provider-specific functionality can be retained. For instance, if a given provider provides functions or provider-specific features, parsingcomponent116 can retain enough information to retain those functions or features when the data is provided to the user. This is indicated byblock189 inFIG. 2. The parsing can take a wide variety of other forms as well, and this is indicated byblock190.
• The parsed data is then provided to commondata model component118.Component118 illustratively places the parsed data into a common data structure and can store it incache115. This is indicated byblock192 of the flow diagram ofFIG. 2. The common data structure can take a wide variety of different forms. However, in one embodiment, the common data structure presents data according to a common structure so that it can be viewed in the same way, byuser108, regardless of the particular data provider that provided the data. Thus,user108 need not become familiar with a wide variety of different data presentation structures that are used to view data in the different data providers. Instead, commondata model component118 places the data into a common data structure that is then provided toclient110. Sending the common data structure toclient110 is indicated byblock194 inFIG. 2.
• The data can be sent in a variety of different ways, and it can be subjected to various optimizations. For instance, theclient communication component122 can illustratively download more than the requested data and store it incache115.Component122 can then send only part of the data, and then send additional parts based on client interactions. By way of example, it may be thatclient communication component122 only sends the file folder tree that was obtained fromdata provider104. As the user navigates the file folder tree, additional information will be sent fromcache115 based on the user's navigation inputs. Also, as an example, if a user selects a file,client communication component122 can begin to send that file information, even before the user has requested that it be downloaded. This reduces the latency when the user actually wishes to download the file. Alternatively,client communication component122 can provide the data overAPI136 toclient device110, without optimizing. Providing only part of the data is indicated byblock196 and responding to client requests fromcache115 is indicated byblock198. Providing the data in other ways is indicated byblock200 in the flow diagram ofFIG. 2.
• FIG. 3A shows one embodiment of an entity diagram that represents an AttachmentDataProvider base class that can be implemented indocument sharing system114. In one embodiment, the AttachmentDataProvider has an identifier (or ID) which is passed in by the client to identify the particular data provider from which data is being sought. It also includes a display name which is the actual name of the data provider that is displayed in the common data structure touser108. The GetItems base method is used byclient device110 to make a call with a data identifier (e.g., an attachment identifier) that identifies the specific content in the identified data provider that is requested (e.g., a given file in a given folder, etc.).
• FIG. 3B is a diagram of a type of the AttachmentDataProvider shown inFIG. 3A, but which provides a specific implementation for a specific data provider. In the embodiment shown inFIG. 3B, the implementation is for the ACME data provider, although this is exemplary only. A number of things should be noted. The end point URL indicates the base web address of the provider. The client context is created from this. The CreateAndConfigureClientContext identifies the particular user that the data sharing system is working on behalf of. This information allows the data provider to determine whether the specific user (or client) has access to the requested data. The client context can thus be passed to the data provider with all calls for data.
• The AttachmentDataProvider base class shown inFIG. 3A, and the specific data provider implementation shown inFIG. 3B are exemplary only. A wide variety of different base classes and specific implementations can be used.
• It can thus be seen that by creating a new data type on thee-mail server102 to represent different document store locations (or data providers) the type can be extended with specific implementations for different data stores. The extended class implements the necessary authentication and APIs to complete the processes with a specific location (e.g., with a specific data provider). When theclient110 makes a request to obtain data or to permission a file, it makes the same web service calls overAPI136 to mailserver102, providing the attachment data provider ID.Server102 then uses the extended implementation (124-126) for that provider to complete the requests and return data back toclient110. Because of these abstractions, multiple clients can easily connect with these data provider capabilities by implementing a relatively simple set of APIs, whilemail server102 performs the relatively costly processing to connect to all of the different data stores (or data providers). In addition, new data providers can be added by implementing a set of APIs onmail server102 that can connect to the new data store (or data provider). Substantially the only change needed on the client, when a new data provider is added, is for the client to recognize the new data provider ID. Other than that, theclient110 stays substantially unchanged, even as new data providers are added. That is, even when new data stores are connected to mailstore102,client110 makes substantially the same calls to mailserver102 in order to access information. The only new item forclient110 to access data on the new data provider is forclient110 to pass in the ID of the new data provider.
• The present discussion has mentioned processors and servers. In one embodiment, the processors and servers include computer processors with associated memory and timing circuitry, not separately shown. They are functional parts of the systems or devices to which they belong and are activated by, and facilitate the functionality of the other components or items in those systems.
• Also, a number of user interface displays have been discussed. They can take a wide variety of different forms and can have a wide variety of different user actuatable input mechanisms disposed thereon. For instance, the user actuatable input mechanisms can be text boxes, check boxes, icons, links, drop-down menus, search boxes, etc. They can also be actuated in a wide variety of different ways. For instance, they can be actuated using a point and click device (such as a track ball or mouse). They can be actuated using hardware buttons, switches, a joystick or keyboard, thumb switches or thumb pads, etc. They can also be actuated using a virtual keyboard or other virtual actuators. In addition, where the screen on which they are displayed is a touch sensitive screen, they can be actuated using touch gestures. Also, where the device that displays them has speech recognition components, they can be actuated using speech commands.
• A number of data stores have also been discussed. It will be noted they can each be broken into multiple data stores. All can be local to the systems accessing them, all can be remote, or some can be local while others are remote. All of these configurations are contemplated herein.
• Also, the figures show a number of blocks with functionality ascribed to each block. It will be noted that fewer blocks can be used so the functionality is performed by fewer components. Also, more blocks can be used with the functionality distributed among more components.
• FIG. 4 is a block diagram ofarchitecture100, shown inFIG. 1, except that its elements are disposed in acloud computing architecture500. Cloud computing provides computation, software, data access, and storage services that do not require end-user knowledge of the physical location or configuration of the system that delivers the services. In various embodiments, cloud computing delivers the services over a wide area network, such as the internet, using appropriate protocols. For instance, cloud computing providers deliver applications over a wide area network and they can be accessed through a web browser or any other computing component. Software or components ofarchitecture100 as well as the corresponding data, can be stored on servers at a remote location. The computing resources in a cloud computing environment can be consolidated at a remote data center location or they can be dispersed. Cloud computing infrastructures can deliver services through shared data centers, even though they appear as a single point of access for the user. Thus, the components and functions described herein can be provided from a service provider at a remote location using a cloud computing architecture. Alternatively, they can be provided from a conventional server, or they can be installed on client devices directly, or in other ways.
• The description is intended to include both public cloud computing and private cloud computing. Cloud computing (both public and private) provides substantially seamless pooling of resources, as well as a reduced need to manage and configure underlying hardware infrastructure.
• A public cloud is managed by a vendor and typically supports multiple consumers using the same infrastructure. Also, a public cloud, as opposed to a private cloud, can free up the end users from managing the hardware. A private cloud may be managed by the organization itself and the infrastructure is typically not shared with other organizations. The organization still maintains the hardware to some extent, such as installations and repairs, etc.
• In the embodiment shown inFIG. 4, some items are similar to those shown inFIG. 1 and they are similarly numbered.FIG. 4 specifically shows thatmail server102 and data providers104-106 are located in cloud502 (which can be public, private, or a combination where portions are public while others are private). Therefore,user108 uses aclient device110 to access those systems throughcloud502.
• FIG. 4 also depicts another embodiment of a cloud architecture.FIG. 4 shows that it is also contemplated that some elements ofarchitecture100 are disposed incloud502 while others are not. By way of example, data providers104-106 can be disposed outside ofcloud502, and accessed through cloud502 (inFIG. 4,data provider104 is shown outsidecloud502, in one embodiment). In another embodiment,mail server102 can also be outside of cloud502 (and may be local toclient device110, or located elsewhere). Regardless of where they are located, they can be accessed directly bydevice110, through a network (either a wide area network or a local area network), they can be hosted at a remote site by a service, or they can be provided as a service through a cloud or accessed by a connection service that resides in the cloud. All of these architectures are contemplated herein.
• It will also be noted thatarchitecture100, or portions of it, can be disposed on a wide variety of different devices. Some of those devices include servers, desktop computers, laptop computers, tablet computers, or other mobile devices, such as palm top computers, cell phones, smart phones, multimedia players, personal digital assistants, etc.
• FIG. 5 is a simplified block diagram of one illustrative embodiment of a handheld or mobile computing device that can be used as a user's or client's hand helddevice16, in which architecture100 (or parts of it) can be deployed.FIGS. 6-9 are examples of handheld or mobile devices.
• FIG. 5 provides a general block diagram of the components of aclient device16 that can run components ofarchitecture100 or that interacts witharchitecture100, or both. In thedevice16, acommunications link13 is provided that allows the handheld device to communicate with other computing devices and under some embodiments provides a channel for receiving information automatically, such as by scanning. Examples of communications link13 include an infrared port, a serial/USB port, a cable network port such as an Ethernet port, and a wireless network port allowing communication though one or more communication protocols including General Packet Radio Service (GPRS), LTE, HSPA, HSPA+ and other 3G and 4G radio protocols, 1Xrtt, and Short Message Service, which are wireless services used to provide cellular access to a network, as well as 802.11 and 802.11b (Wi-Fi) protocols, and Bluetooth protocol, which provide local wireless connections to networks.
• Under other embodiments, applications or systems are received on a removable Secure Digital (SD) card that is connected to aSD card interface15.SD card interface15 andcommunication links13 communicate with a processor17 (which can also embodyprocessors112 or138 fromFIG. 1) along abus19 that is also connected to memory21 and input/output (I/O)components23, as well asclock25 andlocation system27.
• I/O components23, in one embodiment, are provided to facilitate input and output operations. I/O components23 for various embodiments of thedevice16 can include input components such as buttons, touch sensors, multi-touch sensors, optical or video sensors, voice sensors, touch screens, proximity sensors, microphones, tilt sensors, and gravity switches and output components such as a display device, a speaker, and or a printer port. Other I/O components23 can be used as well.
• Clock25 illustratively comprises a real time clock component that outputs a time and date. It can also, illustratively, provide timing functions forprocessor17.
• Location system27 illustratively includes a component that outputs a current geographical location ofdevice16. This can include, for instance, a global positioning system (GPS) receiver, a LORAN system, a dead reckoning system, a cellular triangulation system, or other positioning system. It can also include, for example, mapping software or navigation software that generates desired maps, navigation routes and other geographic functions.
• Memory21stores operating system29,network settings31,applications33,application configuration settings35,data store37,communication drivers39, andcommunication configuration settings41. Memory21 can include all types of tangible volatile and non-volatile computer-readable memory devices. It can also include computer storage media (described below). Memory21 stores computer readable instructions that, when executed byprocessor17, cause the processor to perform computer-implemented steps or functions according to the instructions. Similarly,device16 can have a client business system24 which can run various business applications or embody parts or all oftenant104.Processor17 can be activated by other components to facilitate their functionality as well.
• Examples of thenetwork settings31 include things such as proxy information, Internet connection information, and mappings.Application configuration settings35 include settings that tailor the application for a specific enterprise or user.Communication configuration settings41 provide parameters for communicating with other computers and include items such as GPRS parameters, SMS parameters, connection user names and passwords.
• Applications33 can be applications that have previously been stored on thedevice16 or applications that are installed during use, although these can be part ofoperating system29, or hosted external todevice16, as well.
• FIG. 6 shows one embodiment in whichdevice16 is atablet computer600. InFIG. 6,computer600 is shown with userinterface display screen602.Screen602 can be a touch screen (so touch gestures from a user's finger can be used to interact with the application) or a pen-enabled interface that receives inputs from a pen or stylus. It can also use an on-screen virtual keyboard. Of course, it might also be attached to a keyboard or other user input device through a suitable attachment mechanism, such as a wireless link or USB port, for instance.Computer600 can also illustratively receive voice inputs as well.
• FIGS. 7 and 8 provide additional examples ofdevices16 that can be used, although others can be used as well. InFIG. 7, a feature phone, smart phone ormobile phone45 is provided as thedevice16.Phone45 includes a set ofkeypads47 for dialing phone numbers, adisplay49 capable of displaying images including application images, icons, web pages, photographs, and video, andcontrol buttons51 for selecting items shown on the display. The phone includes anantenna53 for receiving cellular phone signals such as General Packet Radio Service (GPRS) and 1Xrtt, and Short Message Service (SMS) signals. In some embodiments,phone45 also includes a Secure Digital (SD) card slot55 that accepts aSD card57.
• The mobile device ofFIG. 8 is a personal digital assistant (PDA)59 or a multimedia player or a tablet computing device, etc. (hereinafter referred to as PDA59).PDA59 includes aninductive screen61 that senses the position of a stylus63 (or other pointers, such as a user's finger) when the stylus is positioned over the screen. This allows the user to select, highlight, and move items on the screen as well as draw and write.PDA59 also includes a number of user input keys or buttons (such as button65) which allow the user to scroll through menu options or other display options which are displayed ondisplay61, and allow the user to change applications or select user input functions, without contactingdisplay61. Although not shown,PDA59 can include an internal antenna and an infrared transmitter/receiver that allow for wireless communication with other computers as well as connection ports that allow for hardware connections to other computing devices. Such hardware connections are typically made through a cradle that connects to the other computer through a serial or USB port. As such, these connections are non-network connections. In one embodiment,mobile device59 also includes aSD card slot67 that accepts aSD card69.
• FIG. 9 is similar toFIG. 7 except that the phone is asmart phone71.Smart phone71 has a touchsensitive display73 that displays icons or tiles or other user input mechanisms75. Mechanisms75 can be used by a user to run applications, make calls, perform data transfer operations, etc. In general,smart phone71 is built on a mobile operating system and offers more advanced computing capability and connectivity than a feature phone.
• Note that other forms of thedevices16 are possible.
• FIG. 10 is one embodiment of a computing environment in whicharchitecture100, or parts of it, (for example) can be deployed. With reference toFIG. 10, an exemplary system for implementing some embodiments includes a general-purpose computing device in the form of acomputer810. Components ofcomputer810 may include, but are not limited to, a processing unit820 (which can compriseprocessor112 or138), asystem memory830, and asystem bus821 that couples various system components including the system memory to theprocessing unit820. Thesystem bus821 may be any of several types of bus structures including a memory bus or memory controller, a peripheral bus, and a local bus using any of a variety of bus architectures. By way of example, and not limitation, such architectures include Industry Standard Architecture (ISA) bus, Micro Channel Architecture (MCA) bus, Enhanced ISA (EISA) bus, Video Electronics Standards Association (VESA) local bus, and Peripheral Component Interconnect (PCI) bus also known as Mezzanine bus. Memory and programs described with respect toFIG. 1 can be deployed in corresponding portions ofFIG. 10.
• Computer810 typically includes a variety of computer readable media. Computer readable media can be any available media that can be accessed bycomputer810 and includes both volatile and nonvolatile media, removable and non-removable media. By way of example, and not limitation, computer readable media may comprise computer storage media and communication media. Computer storage media is different from, and does not include, a modulated data signal or carrier wave. It includes hardware storage media including both volatile and nonvolatile, removable and non-removable media implemented in any method or technology for storage of information such as computer readable instructions, data structures, program modules or other data. Computer storage media includes, but is not limited to, RAM, ROM, EEPROM, flash memory or other memory technology, CD-ROM, digital versatile disks (DVD) or other optical disk storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other medium which can be used to store the desired information and which can be accessed bycomputer810. Communication media typically embodies computer readable instructions, data structures, program modules or other data in a transport mechanism and includes any information delivery media. The term “modulated data signal” means a signal that has one or more of its characteristics set or changed in such a manner as to encode information in the signal. By way of example, and not limitation, communication media includes wired media such as a wired network or direct-wired connection, and wireless media such as acoustic, RF, infrared and other wireless media. Combinations of any of the above should also be included within the scope of computer readable media.
• Thesystem memory830 includes computer storage media in the form of volatile and/or nonvolatile memory such as read only memory (ROM)831 and random access memory (RAM)832. A basic input/output system833 (BIOS), containing the basic routines that help to transfer information between elements withincomputer810, such as during start-up, is typically stored in ROM831.RAM832 typically contains data and/or program modules that are immediately accessible to and/or presently being operated on by processingunit820. By way of example, and not limitation,FIG. 10 illustratesoperating system834,application programs835,other program modules836, andprogram data837.
• Thecomputer810 may also include other removable/non-removable volatile/nonvolatile computer storage media. By way of example only,FIG. 10 illustrates ahard disk drive841 that reads from or writes to non-removable, nonvolatile magnetic media, a magnetic disk drive851 that reads from or writes to a removable, nonvolatilemagnetic disk852, and anoptical disk drive855 that reads from or writes to a removable, nonvolatileoptical disk856 such as a CD ROM or other optical media. Other removable/non-removable, volatile/nonvolatile computer storage media that can be used in the exemplary operating environment include, but are not limited to, magnetic tape cassettes, flash memory cards, digital versatile disks, digital video tape, solid state RAM, solid state ROM, and the like. Thehard disk drive841 is typically connected to thesystem bus821 through a non-removable memory interface such asinterface840, and magnetic disk drive851 andoptical disk drive855 are typically connected to thesystem bus821 by a removable memory interface, such asinterface850.
• Alternatively, or in addition, the functionality described herein can be performed, at least in part, by one or more hardware logic components. For example, and without limitation, illustrative types of hardware logic components that can be used include Field-programmable Gate Arrays (FPGAs), Program-specific Integrated Circuits (ASICs), Program-specific Standard Products (ASSPs), System-on-a-chip systems (SOCs), Complex Programmable Logic Devices (CPLDs), etc.
• The drives and their associated computer storage media discussed above and illustrated inFIG. 10, provide storage of computer readable instructions, data structures, program modules and other data for thecomputer810. InFIG. 10, for example,hard disk drive841 is illustrated as storingoperating system844,application programs845,other program modules846, andprogram data847. Note that these components can either be the same as or different fromoperating system834,application programs835,other program modules836, andprogram data837.Operating system844,application programs845,other program modules846, andprogram data847 are given different numbers here to illustrate that, at a minimum, they are different copies.
• A user may enter commands and information into thecomputer810 through input devices such as akeyboard862, amicrophone863, and apointing device861, such as a mouse, trackball or touch pad. Other input devices (not shown) may include a joystick, game pad, satellite dish, scanner, or the like. These and other input devices are often connected to theprocessing unit820 through auser input interface860 that is coupled to the system bus, but may be connected by other interface and bus structures, such as a parallel port, game port or a universal serial bus (USB). Avisual display891 or other type of display device is also connected to thesystem bus821 via an interface, such as avideo interface890. In addition to the monitor, computers may also include other peripheral output devices such asspeakers897 andprinter896, which may be connected through an outputperipheral interface895.
• Thecomputer810 is operated in a networked environment using logical connections to one or more remote computers, such as aremote computer880. Theremote computer880 may be a personal computer, a hand-held device, a server, a router, a network PC, a peer device or other common network node, and typically includes many or all of the elements described above relative to thecomputer810. The logical connections depicted inFIG. 10 include a local area network (LAN)871 and a wide area network (WAN)873, but may also include other networks. Such networking environments are commonplace in offices, enterprise-wide computer networks, intranets and the Internet.
• When used in a LAN networking environment, thecomputer810 is connected to theLAN871 through a network interface oradapter870. When used in a WAN networking environment, thecomputer810 typically includes amodem872 or other means for establishing communications over theWAN873, such as the Internet. Themodem872, which may be internal or external, may be connected to thesystem bus821 via theuser input interface860, or other appropriate mechanism. In a networked environment, program modules depicted relative to thecomputer810, or portions thereof, may be stored in the remote memory storage device. By way of example, and not limitation,FIG. 10 illustratesremote application programs885 as residing onremote computer880. It will be appreciated that the network connections shown are exemplary and other means of establishing a communications link between the computers may be used.
• It should also be noted that the different embodiments described herein can be combined in different ways. That is, parts of one or more embodiments can be combined with parts of one or more other embodiments. All of this is contemplated herein.
• Although the subject matter has been described in language specific to structural features and/or methodological acts, it is to be understood that the subject matter defined in the appended claims is not necessarily limited to the specific features or acts described above. Rather, the specific features and acts described above are disclosed as example forms of implementing the claims.

Claims (21)

1-20. (canceled)

21. A computer-implemented method, comprising:

receiving a request for message data, the request being associated with a client device;

based on the request:

obtaining first message data from a first data provider, the first message data corresponding to a first data structure, and

obtaining second message data from a second data provider, the second message data corresponding to a second data structure that is different than the first data structure;

placing the first message data and the second message data in a common data structure that is associated with the client device and defines a single presentation view for Tendering the first and second message data on the client device; and

providing the first and second message data in the common data structure to the client device.

22. The computer-implemented method ofclaim 21, wherein the first data structure is generated by the first data provider, the second data structure is generated by the second data provider, and wherein the first data provider is different than the second data provider.

23. The computer-implemented method ofclaim 22, wherein the common data structure defines a same data structure that is the same regardless of the first and second data structures being generated by the first and second data providers from which message data is obtained, respectively.

24. The computer-implemented method ofclaim 21, wherein placing the first message data and the second message data in the common data structure comprises:

parsing the first message data and the second message data into correspondingly parsed portions; and

placing the parsed portions into the common data structure.

25. The computer-implemented method ofclaim 21, wherein the first message data obtained from the first data provider corresponds to a first message, and the second message data obtained from the second data provider corresponds to a second message that is separate from the first message.

26. The computer-implemented method ofclaim 21, wherein the first message data corresponds to a first portion of a particular message associated with a user, and the second message data corresponds to a second portion of the particular message.

27. The computer-implemented method ofclaim 26, wherein the first portion of the message corresponds to a first type of content, and the second portion of the message corresponds to a second type of content.

28. The computer-implemented method ofclaim 27, wherein the first type of content comprises content included in the message and wherein the second type of content comprises content attached to the message.

29. The computer-implemented method ofclaim 21, wherein the client device comprises a first client device, and further comprising:

based on the request, identifying a particular user account;

identifying one or more other client devices, other than the first client device, associated with the particular user account; and

providing the first and second message data in the common data structure to the first client device and the one more other client devices such that the first and second message data is rendered in the same single presentation view across the client devices.

30. A computing system comprising:

a processor; and

memory storing instructions executable by the processor, wherein the instructions, when executed, configure the computing system to:

receive a first request for message data associated with a first message;

based on the first request, obtain first message data from a first data provider that corresponds to a first data structure;

receive a second request for message data associated with a second message;

based on the second request, obtain second message data from a second data provider that corresponds to a second data structure that is different than the first data structure;

place the first message data and the second message data in a common data structure that defines a single presentation view for rendering the first and second message data on a client device associated with the first and second message; and

provide the first and second message data in the common data structure to the client device.

31. The computing system ofclaim 30, wherein the instructions configure the computing system to;

define the common data structure as a same structure of data, that is the same regardless of the first and second data structures associated with the first and second data providers from which the first and second message data is obtained, respectively.

32. The computing system ofclaim 30, wherein the instructions configure the computing system to:

parse the first and second message data into correspondingly parsed portions; and

placing the parsed portions in the common data structure.

33. The computing system ofclaim 30, wherein the client device comprises a first client device, and wherein the instructions configure the computing system to:

identify the first message as being associated with the first client device; and

identify the second message as being associated with a second client device.

34. The computing system ofclaim 33, wherein the instructions configure the computing system to:

place the first message data and the second Message data in the common data structure for rendering the first and second message data in a same presentation style across the first client device and the second client device.

35. The computing system ofclaim 34, wherein the same presentation style provides a similar visual representation of the first message data and the second message data across the first client device and the second client device.

36. The computing system ofclaim 30, wherein the instructions configure the computing system to:

expose by a first data provider implementation, a first application programming interface configured to interact with the first data provider to obtain the first message data; and

expose, by a second data provider implementation, a second application programming interface configured to interact with the second data provider to obtain the second message data.

37. The computing system ofclaim 32, wherein the instructions configure the computing system to:

parse the first message data using first provider-specific parsing to identify a portion of the first message data to be included in the common data structure; and

parse the second message data using second provider-specific parsing to identify a portion of the second message data to be included in the common data structure.

38. A computing system comprising:

a communication component configured to receive a request for message data associated with a client device;

a data provider identifier component configured to, based on the request for message data:

identify a first data provider to obtain first message data having a first data structure, and

identify a second data provider to obtain second message data having a second data structure, the second data structure being different than the first data structure;

a common data model component configured to place the first message data and the second message data in a common data structure that defines a single presentation view for rendering the first and second message data on the client device; and

wherein the client communication component is configured to provide, to the client device, the first and second message data in the common data structure.

39. The computing system ofclaim 38, wherein the first message data corresponds to a first type of message content, and the second message data corresponds to a second type of message content, the second type being different than the first type.

40. The computing system ofclaim 39, wherein the data provider identifier is configured to:

identify the first data provider as a provider of the first type of message content, and

identify the second data provider as a provider of the second type of message content, wherein the second type of message content comprises a message attachment.

Images