Abstract: An apparatus for working a wet coating, such as render material, applied to a surface, the apparatus comprising: an actuator arranged to move an arm across a surface having a wet coating applied thereon; a controller configured to move the arm across the surface along a tool path; and a tool head mounted to the arm, the tool head comprising a compliance module and a tool mounted to the compliance module such that the tool is movable in a stroke direction towards the surface relative to the arm. The compliance module comprises a biasing module arranged to urge the tool in the stroke direction to maintain contact between the tool and the wet coating such that the tool works the wet coating as the arm moves across the surface.

Abstract: File system-awareness of ghosting performed by one or more tiering engines allows a file system to receive and store metadata indicating an identifier of the tiering engine ghosting the file extents and a storage location of the ghosted file extents for later use by the tiering engine. The file system is able to receive and process requests to read and write to a file having ghosted extents.

Abstract: Described are embodiments directed at persistent handles that are used to retain state across network failures and server failovers. Persistent handles are requested by a client after a session has been established with a file server. The request for the persistent handle includes a handle identifier generated by the client. The server uses the handle identifier to associate with state information. When there is a network failure or a server failover, and a reconnection to the client, the handle identifier is used to identify replayed requests that if replayed would create an inconsistent state on the server. The replayed requests are then appropriately handled.

Abstract: Described are embodiments directed at persistent handles that are used to retain state across network failures and server failovers. Persistent handles are requested by a client after a session has been established with a file server. The request for the persistent handle includes a handle identifier generated by the client. The server uses the handle identifier to associate with state information. When there is a network failure or a server failover, and a reconnection to the client, the handle identifier is used to identify replayed requests that if replayed would create an inconsistent state on the server. The replayed requests are then appropriately handled.

Abstract: Described are embodiments directed at persistent handles that are used to retain state across network failures and server failovers. Persistent handles are requested by a client after a session has been established with a file server. The request for the persistent handle includes a handle identifier generated by the client. The server uses the handle identifier to associate with state information. When there is a network failure or a server failover, and a reconnection to the client, the handle identifier is used to identify replayed requests that if replayed would create an inconsistent state on the server. The replayed requests are then appropriately handled.

Abstract: Described are embodiments directed at persistent handles that are used to retain state across network failures and server failovers. Persistent handles are requested by a client after a session has been established with a file server. The request for the persistent handle includes a handle identifier generated by the client. The server uses the handle identifier to associate with state information. When there is a network failure or a server failover, and a reconnection to the client, the handle identifier is used to identify replayed requests that if replayed would create an inconsistent state on the server. The replayed requests are then appropriately handled.