US 12,289,370 B2
Systems and methods for building and providing polymorphic rest services for heterogeneous repositories
Wei Zhou, Shanghai (CN); Muhua Chen, Shanghai (CN); Wei Ruan, Shanghai (CN); and Chen Wang, Shanghai (CN)
Assigned to OPEN TEXT CORPORATION, Waterloo (CA)
Filed by OPEN TEXT CORPORATION, Waterloo (CA)
Filed on May 1, 2024, as Appl. No. 18/651,953.
Application 18/651,953 is a continuation of application No. 18/342,657, filed on Jun. 27, 2023, granted, now 12,010,198.
Application 18/342,657 is a continuation of application No. 17/572,511, filed on Jan. 10, 2022, granted, now 11,722,582, issued on Aug. 8, 2023.
Application 17/572,511 is a continuation of application No. 17/158,154, filed on Jan. 26, 2021, granted, now 11,223,701, issued on Jan. 11, 2022.
Application 17/158,154 is a continuation of application No. 16/854,624, filed on Apr. 21, 2020, granted, now 10,938,953, issued on Mar. 2, 2021.
Application 16/854,624 is a continuation of application No. 16/057,549, filed on Aug. 7, 2018, granted, now 10,652,361, issued on May 12, 2020.
Claims priority of provisional application 62/543,092, filed on Aug. 9, 2017.
Prior Publication US 2024/0291908 A1, Aug. 29, 2024
This patent is subject to a terminal disclaimer.
Int. Cl. H04L 67/1097 (2022.01); G06F 16/25 (2019.01); G06F 16/951 (2019.01); H04L 41/5041 (2022.01); H04L 67/01 (2022.01); H04L 67/02 (2022.01); H04L 67/133 (2022.01); H04L 67/563 (2022.01); H04L 67/61 (2022.01); H04L 67/63 (2022.01)
CPC H04L 67/1097 (2013.01) [G06F 16/252 (2019.01); G06F 16/951 (2019.01); H04L 41/5041 (2013.01); H04L 67/01 (2022.05); H04L 67/02 (2013.01); H04L 67/133 (2022.05); H04L 67/61 (2022.05); H04L 67/63 (2022.05); H04L 67/563 (2022.05)] 20 Claims
OG exemplary drawing
 
1. A method, comprising:
in a client-server architecture having a client side and a server side, building a Representational State Transfer (REST) extension at the client side and, at the server side, providing a REST server with an ability to decide, by and within the REST server, which universal resource identifier (URI) contained in incoming REST requests to reject, accept, or redirect,
wherein the ability is based on knowledge gained by the REST server at implementation time and at runtime,
wherein a REST application programming interface (API) is customized with configuration parameters for the REST extension and deployed to enterprise-provisioned repositories at the implementation time, and
wherein a resource registry model is created at the runtime, the resource registry model governing resource endpoints registered with the REST server and used by the REST server to make decisions in the REST server's internal request handling flow, including:
receiving an incoming REST request, the incoming REST request indicating a resource in a target repository, the resource having a URI;
querying the resource registry model or the target repository for a repository type of the target repository so as to gain knowledge on whether the resource is available to the target repository at the runtime, regardless of whether the target repository is a default repository or an enterprise-provisioned repository; and
based at least on the queried repository type, determining whether to accept, reject, or redirect the incoming REST request.