Workspace resiliency with multi-feed status resource caching
OwnerGeorgy Momchilov, Avijit Gahtori +1inventors
InventorsGeorgy Momchilov, Avijit Gahtori, Mukund Ingale
Life of this patent
Estimating the term…
Abstract
A client device includes resource caches, and a processor coupled to the resource caches. The processor receives resources from different resource feeds, and caches user interfaces (UI) of the resources from the different resource feeds, with at least one resource feed having a resource cache separate from the resource cache of the other resource feeds. Statuses of the resource feeds are determined, with at least one status indicating availability of the at least one resource feed having the separate resource cache. UI elements from the separate resource cache are retrieved for display in response to the at least one resource feed associated with the separate resource cache not being available.
Claims20
A client device comprising:
- a plurality of resource caches;
- and
- a processor coupled to said plurality of resource caches, and configured to perform the following:
- receive resources from a plurality of different resource feeds,
- cache user interfaces (UI) of the resources from the plurality of different resource feeds, with at least one resource feed having a resource cache separate from the resource cache of the other resource feeds,
- determine status of the resource feeds, with at least one status indicating availability of the at least one resource feed having the separate resource cache,
- retrieve UI elements from the separate resource cache in response to the at least one resource feed associated with the separate resource cache not being available, and
- display the retrieved UI elements from the separate resource cache;
- wherein user authentication to launch at least one of the resources is provided by using an authentication protocol or by using a connection lease, and wherein said processor is configured to perform the following:
- start with using the authentication protocol first before falling back to the connection lease in response to the at least one resource feed providing the resource to be launched being available;
- and
- start with using the connection lease first before falling back to the authentication protocol in response to the at least one resource feed providing the resource to be launched not being available.
A method comprising:
- receiving resources from a plurality of different resource feeds;
- caching user interfaces (UI) of the resources from the plurality of different resource feeds, with at least one resource feed having a resource cache separate from the resource cache of the other resource feeds;
- determining status of the resource feeds, with at least one status indicating availability of the at least one resource feed having the separate resource cache;
- retrieving UI elements from the separate resource cache in response to the at least one resource feed associated with the separate resource cache not being available;
- and
- displaying the retrieved UI elements from the separate resource cache;
- wherein user authentication to launch at least one of the resources is provided by using an authentication protocol or by using a connection lease, and further comprising:
- starting with using the authentication protocol first before falling back to the connection lease in response to the at least one resource feed providing the resource to be launched being available;
- and
- starting with using the connection lease first before falling back to the authentication protocol in response to the at least one resource feed providing the resource to be launched not being available.
A computing system comprising:
- a server configured to receive resources from a plurality of different resource feeds;
- and
- a client device configured to perform the following:
- cache user interfaces (UI) of the resources from the plurality of different resource feeds, with at least one resource feed having a resource cache separate from the resource cache of the other resource feeds,
- determine status of the resource feeds, with at least one status indicating availability of the at least one resource feed having the resource cache separate from the resource cache of the other resource feeds,
- in response to the at least one resource feed having the resource cache separate from the resource cache of the other resource feeds not being available,
- retrieve UI elements from the resource cache that is separate from the resource caches of the other resource feeds, and
- display the retrieved UI elements from the separate resource cache;
- wherein user authentication to launch at least one of the resources is provided by using an authentication protocol or by using a connection lease, and further comprising:
- starting with using the authentication protocol first before falling back to the connection lease in response to the at least one resource feed providing the resource to be launched being available;
- and
- starting with using the connection lease first before falling back to the authentication protocol in response to the at least one resource feed providing the resource to be launched not being available.
Dependencies are inferred from the claim text.