ENCAPSULATION OF ONLINE STORAGE PROVIDERS

• US 20090157841A1
• Filed: 12/14/2007
• Published: 06/18/2009
• Est. Priority Date: 12/14/2007
• Status: Abandoned Application

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Corporation
• Inventors: Wright, Eric Jonathan, Turner, Richard Shailer JR., Siddhartha, Pradyumna, Setiadi, Ignatius
• Application Number:
  US11/957,134
• Publication Number:
  US 20090157841A1
• Time in Patent Office: Days
• US Class Current: 709/217
• CPC Class Codes: G06F 16/958 Organisation or management of web site content, e.g. publishing, maintaining pages or automatic linking

Abstract

A media publisher manager generates a plug-in for each of a plurality of providers. Each provider hosts a web space including a media object and implements a plurality of services related to the media object. Executing the plug-in causes at least one of the plurality of services related to the media object to be performed on at least one of plurality of providers. The media publisher manager request is receives from a client. The request includes a function related to a media object and a moniker of the media object. The moniker is generated from a media object identifier and a provider identifier. A plug-in is selected based on the provider identifier of the moniker. Executing the selected plug-in causes a service related to the media object to be preformed on the provider, said service related to the requested function.

Claims

1. A method for publishing media objects to a provider, comprising:

identifying a plurality of plug-ins, one corresponding to each of a plurality of the providers, each of the providers hosting a web space including a media object, each of the providers implementing a plurality of services related to the media object, wherein executing the corresponding plug-in for a particular provider causes at least one of the plurality of services of the particular provider related to the media object to be performed on the particular provider;

receiving a request from a client, said request including a function related to a media object;

selecting one of the plurality of plug-ins to execute based on the included function;

executing the selected plug-in, wherein executing the selected plug-in causes a service related to the media object to be performed on the provider, said service related to the requested function;

receiving a status from the provider, said status indicating the success of the performed service; and

sending the status from the provider to the client, said status indicating the success of the request.

2. The method of claim 1, wherein the requested function includes the uploading of the media object to the provider, and further comprising:

selecting one of the plurality of plug-ins to execute to upload the media object;

executing the selected plug-in, wherein executing the selected plug-in causes the provider to upload the media object from the client;

receiving a moniker for the uploaded media object from the provider in response to the execution of the plug-in, said moniker being generated by the provider in response to the uploading of the media object, said moniker including the uploaded media object identifier and a provider identifier, said provider identifier associated with the at least one of the providers which uploaded the media object, said media object identifier representing the uploaded media object in the abstract namespace of the provider; and

sending the moniker to the client wherein the client references the uploaded media object via the moniker.

3. The method of claim 2, wherein the moniker is in a serialized form.

4. The method of claim 1, wherein the request includes a moniker of the media object, said moniker generated from a media object identifier and a provider identifier, said moniker being provided a first provider, said first provider hosting the media object associated with the media identifier, said provider identifier associated with the at least one of the providers, further comprising:

determining the provider identifier from the moniker included in the request;

selecting a plug-in to execute from the generated plug-ins based on the included function and the provider identifier;

executing the selected plug-in, wherein executing the selected plug-in causes a service related to the media object to be performed on the provider, said service related to the requested function and the determined media object identifier;

receiving a status from the provider, said status indicating the success of the performed service; and

sending the status from the provider to the client, said status indicating the success of the request.

5. The method of claim 4, wherein the moniker is in a serialized form.

6. The method of claim 1, wherein the media object includes one or more of the following:

a digital photograph, a digital video, a digital sound recording, and a document.

7. The method of claim 1, wherein the function includes one or more of the following:

Publish a media object to a provider;

remove a media object from a provider, download a media object from a provider, subscribe to a media object of a provider, list the media objects published, list the providers that have invited the client to subscribe, and list the media objects subscribed.

8. The method of claim 1, wherein status is received asynchronously from the provider.

9. The method of claim 1, wherein media objects are related to social networking.

10. The method of claim 1, wherein the plug-in utilizes one or more of the following protocols to communicate with provider:

SOAP, RSS, HTTP, telnet.

11. A method for publishing media objects to a provider, comprising:

generating a plug-in for each of a plurality of providers, each provider hosting a web space including a media object, each provider implementing a plurality of services related to the media object, wherein executing the plug-in causes at least one of the plurality of services related to the media object to be performed on at least one of plurality of providers;

receiving a request from a client, said request including a function related to a media object, said request including a moniker of the media object, said moniker generated from a media object identifier and a provider identifier, said moniker being provided a first provider, said first provider hosting the media object associated with the media identifier, said provider identifier associated with the at least one of the providers;

determining the provider identifier from the moniker included in the request;

selecting a plug-in to execute from the generated plug-ins based on the included function and the provider identifier;

executing the selected plug-in, wherein executing the selected plug-in causes a service related to the media object to be performed on the provider, said service related to the requested function;

receiving a status from the provider, said status indicating the success of the performed service; and

sending the status from the provider to the client, said status indicating the success of the request.

12. The method of claim 11, wherein the requested function includes the downloading of the media object to the provider, further comprising:

selecting a plug-in to execute from the generated plug-ins to download the media object from the provider associated with the determined provider identifier; and

executing the selected plug-in, wherein executing the selected plug-in causes the provider to download the media object to the client.

13. The method of claim 11, wherein the moniker is in a serialized form.

14. The method of claim 11, wherein the media object includes one or more of the following:

a digital photograph, a digital video, a digital sound recording, and a document.

15. The method of claim 11, wherein the function includes one or more of the following:

Publish a media object to a provider;

remove a media object from a provider, download a media object from a provider, subscribe to a media object of a provider, list the media objects published, list the providers that have invited the client to subscribe, and list the media objects subscribed.

16. The method of claim 11, wherein status is received asynchronously from the provider.

17. The method of claim 11, wherein media objects are related to social networking.

18. The method of claim 11, wherein the plug-in utilizes one or more of the following protocols to communicate with provider:

SOAP, RSS, HTTP, telnet.

19. A application program interface (API) for publishing media objects to a provider, comprising computer readable instructions for:

generating a plug-in for each of a plurality of providers, each provider hosting a web space including a media object, each provider implementing a plurality of services related to the media object, wherein executing the plug-in causes at least one of the plurality of services related to the media object to be performed on at least one of plurality of providers;

receiving a first request from a client, said first request including the uploading of a media object;

selecting a plug-in to execute from the generated plug-ins to upload the media object;

executing the selected plug-in, wherein executing the selected plug-in causes the provider to upload the media object from the client;

receiving a moniker for the uploaded media object from the provider in response to the execution of the plug-in, said moniker being generated by the provider in response to the uploading of the media object, said moniker including the uploaded media object identifier and a provider identifier, said provider identifier associated with the at least one of the providers which uploaded the media object; and

sending the moniker to the client wherein the client references the uploaded media object via the moniker

receiving a status from the provider, said status indicating the success of the performed service; and

sending the status from the provider to the client, said status indicating the success of the first request.

receiving a second request including a function related to the media object and the moniker of the media object;

determining the provider identifier from the moniker included in the second request;

selecting a plug-in to execute from the generated plug-ins based on the included function and the provider identifier;

executing the selected plug-in, wherein executing the selected plug-in causes a service related to the media object to be performed on the provider, said service related to the requested function and the determined media object identifier;

receiving a status from the provider, said status indicating the success of the performed service; and

sending the status from the provider to the client, said status indicating the success of the second request.

20. The API of claim 19, wherein the plug-in utilizes one or more of the following protocols to communicate with provider:

SOAP, RSS, HTTP, telnet.