Back to results
US 11,451,839 B1Granted
System and method for client side compression in a content management environment
AssigneeOpen Text Holdings, Inc.
InventorsVenkatesh Nandikalkere Giriyappa, Vidya Ellur, Roginy Balasubramanian
Life of this patent
Estimating the term…
Abstract
Embodiments of content management systems in which compression and decompression may be performed at the client in cases where the client device or application may be capable of such compression and decompression while still allowing compression to be performed at the content management system when client devices or applications are unable to perform such compression or decompression are disclosed.
Claims14
A content management system, comprising:
- a data store including:
- a first data repository storing compressed content;
- a second data repository storing uncompressed content;
- and
- a metadata repository, comprising document compression metadata;
- and
- a content management server, comprising a non-transitory computer readable medium comprising instructions for:
- receiving, from a client application, an access request in association with first content in the data store;
- accessing the document compression metadata to determine that the first content is associated with compression;
- when it is determined that the first content is associated with compression, returning metadata to the client application, the metadata including first compression metadata for that first content indicating that compression is enabled for the first content;
- receiving, from the client application, a write request to write the content to the content management system, wherein the write request includes the first content;
- determining if a client compression indicator is included in the write request;
- when there is no client compression indicator in the write request:
- determining if the first content should be compressed based on the document compression metadata;
- when it is determined the first content should be compressed:
- compressing the first content at the content management system;
- and
- storing the compressed first content in the first repository;
- when it is determined that the first content should not be compressed, storing the content in the second repository;
- and
- when there is the client compression indicator in the write request:
- determining that the client compression indicator indicates that the first content is compressed;
- and
- storing the first content directly in the first data repository, wherein the first content was compressed at the client application and the client compression indicator was set at the client application.
21 more elements
A content management system, comprising:
- a data store including:
- a first data repository storing compressed content;
- a second data repository storing uncompressed content;
- and
- a metadata repository, comprising document compression metadata;
- and
- a content management server, comprising a non-transitory computer readable medium comprising instructions for:
- receiving, from a client application, an access request in association with first content in the data store;
- determining if the access request includes a client compression indicator set at the client application;
- when there is no client compression indicator in the access request:
- determining if the first content is compressed based on the document compression metadata;
- when it is determined the first content is compressed, decompressing the first content at the content management system, and returning the decompressed first content from the first repository;
- when there is a client compression indicator in the access request:
- determining if the first content is compressed based on the document compression metadata;
- determining that the client compression indicator indicates that decompression will be performed at the client application;
- and
- returning the first content directly to the first client from the first data repository and returning first compression metadata for that first content indicating that the first content is compressed, wherein the client application is adapted to decompress the first content at the client application.
14 more elements
A method, comprising:
- receiving at a content management server, from a client application, an access request in association with first content in a data store, the data store including a first data repository storing compressed content, a second data repository storing uncompressed content and a metadata repository, comprising document compression metadata;
- accessing the document compression metadata to determine that the first content is associated with compression;
- when it is determined that the first content is associated with compression, returning metadata to the client application, the metadata including first compression metadata for that first content indicating that compression is enabled for the first content;
- receiving, from the client application, a write request to write the content to the content management system, wherein the write request includes the first content;
- determining if a client compression indicator is included in the write request;
- when there is no client compression indicator in the write request:
- determining if the first content should be compressed based on the document compression metadata;
- when it is determined the first content should be compressed:
- compressing the first content at the content management system;
- and
- storing the compressed first content in the first repository;
- when it is determined that the first content should not be compressed, storing the content in the second repository;
- and
- when there is the client compression indicator in the write request:
- determining that the client compression indicator indicates that the first content is compressed;
- and
- storing the first content directly in the first data repository, wherein the first content was compressed at the client application and the client compression indicator was set at the client application.
14 more elements
A method, comprising:
- receiving at a content management server, from a client application, an access request in association with first content in a data store, the data store including a first data repository storing compressed content, a second data repository storing uncompressed content and a metadata repository, comprising document compression metadata;
- determining if the access request includes a client compression indicator set at the client application;
- when there is no client compression indicator in the access request:
- determining if the first content is compressed based on the document compression metadata;
- when it is determined the first content is compressed, decompressing the first content at the content management system, and returning the decompressed first content from the first repository;
- when there is a client compression indicator in the access request:
- determining if the first content is compressed based on the document compression metadata;
- determining that the client compression indicator indicates that decompression will be performed at the client application;
- and
- returning the first content directly to the first client from the first data repository and returning first compression metadata for that first content indicating that the first content is compressed, wherein the client application is adapted to decompress the first content at the client application.
7 more elements
Dependencies are inferred from the claim text.