A computer-implemented method for controlling physical actuators in pervasive computing environments, wherein an actuation space is provided, said actuation space being configured to manage actuation requests and actuation status information, wherein the actuation status information provides information about the status of the actuation requests, wherein at least one resource user sends one or more actuation requests to said actuation space that stores said one or more actuation requests, wherein at least one actuator resource controls at least one physical actuator on the basis of one or more of said actuation requests stored in said actuation space, wherein said at least one actuator resource sends actuation status information corresponding to one or more of said actuation requests to said actuation space, wherein said at least one resource user and said at least one actuator resource share said actuation space, wherein said at least one resource user and said at least one actuator resource are decoupled spatially and/or temporally by updating and accessing said shared actuation space, wherein a monitoring of said actuation requests and/or actuation status information maintained in said actuation space is performed by subscribing to said actuation requests and/or actuation status information, wherein said subscribing is performed by sending subscription requests to said actuation space, wherein said subscription requests include a description of the actuation request and/or a flag indicating whether actuation status information is to be returned if available, wherein said actuation space comprises at least one actuation space resource that manages fragments of the actuation space, a resolver that receives all requests that modify the actuation space, and at least one resource directory employed by said resolver, wherein said at least one resource directory returns the correct actuation space resource to said resolver, wherein said resolver forwards the original actuation request received by an resource user or an actuator resource to said actuation space resource, wherein an actuator resource implements a native legacy interface for a legacy actuator, wherein said native legacy interface intercepts calls from legacy resource users, wherein said calls are forwarded to the legacy actuator resource, and wherein a corresponding actuation request is inserted in said actuation space allowing further resource users to coordinate on the actuation tasks of said actuation request, wherein said actuation space is implemented in a distributed fashion, namely in a hierarchy of actuation subspaces that manage said actuation requests and actuation status information for different and/or predefined geographic areas, wherein before a resource user sends an actuation request, said resource user subscribes or queries the relevant parts in said actuation space, wherein a response of said actuation space indicates whether another actuator resource is already requesting a potentially conflicting actuation task, wherein a conflict resolution resource is provided in case of an actuator resource sends a conflicting actuation request, wherein said conflict resolution resource resolves the conflict by monitoring said actuation space and providing a resolved actuation request being accordingly marked, and wherein a conflict resolution mechanism is provided, wherein said conflict resolution mechanism includes first-in-first-out, overwrite, prioritize and/or task modification mechanisms. at least one actuation space resource that manages fragments of the actuation space, a resolver that receives all requests that modify the actuation space, and at least one resource directory employed by said resolver, wherein said resolver forwards the original actuation request received by an resource user or an actuator resource to said actuation space resource, wherein an actuator resource implements a native legacy interface for a legacy actuator, wherein said native legacy interface intercepts calls from legacy resource users, wherein said calls are forwarded to the legacy actuator resource, and wherein a corresponding actuation request is inserted in said actuation space allowing further resource users to coordinate on the actuation tasks of said actuation request, wherein said actuation space is implemented in a distributed fashion, namely in a hierarchy of actuation subspaces that manage said actuation requests and actuation status information for different and/or predefined geographic areas, wherein before a resource user sends an actuation request, said resource user subscribes or queries the relevant parts in said actuation space, wherein a response of said actuation space indicates whether another actuator resource is already requesting a potentially conflicting actuation task, wherein a conflict resolution resource is provided in case of an actuator resource sends a conflicting actuation request, wherein said conflict resolution resource resolves the conflict by monitoring said actuation space and providing a resolved actuation request being accordingly marked, and wherein a conflict resolution mechanism is provided, wherein said conflict resolution mechanism includes first-in-first-out, overwrite, prioritize and/or task modification mechanisms.