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.

Abstract: Described is the adding of padding to a content file (e.g., image and/or audiovisual file) for anticipated subsequent use such that the content file need not be re-encoded to add metadata and other data to it. For example, padding may be added to an image file directly after an image file directory, whereby the directory can grow as needed into the padded space. Metadata can likewise be added to the padding, e.g., from the opposite direction that the directory extends into the padding. The padding may be added on the first re-encoding of the file, reducing or eliminating the need for subsequent re-encoding. The padding also may be used to track dead space in the file, with adjacent regions of dead space coalesced into a single region of dead space.