Abstract: The present invention provides a mechanism whereby active servers are able to extend their RAM by using memory available in standby servers. This can be achieved, without having to take the servers out of their standby mode, by implementing a memory manager operating in at least one active server and configured to directly access the memory of the servers in standby mode, without requiring the processor of these servers in standby mode to be active. In these servers in standby mode, at least their memory, their network card and their communication means are active, whereas at least their processor is in standby mode.

Abstract: The present invention provides a mechanism whereby active servers are able to extend their RAM by using memory available in standby servers. This can be achieved, without having to take the servers out of their standby mode, by implementing a memory manager operating in at least one active server and configured to directly access the memory of the servers in standby mode, without requiring the processor of these servers in standby mode to be active. In these servers in standby mode, at least their memory, their network card and their communication means are active, whereas at least their processor is in standby mode.

Abstract: The invention relieves an application programmer of the responsibility for managing access rights, by providing application code that is independent of the protection in a chip card. When an application, for example in a docking station, is given access to an object pertaining to another application in a chip card, two capabilities are created respectively in the applications, as objects, to protect all subsequent accesses to the object by filtering them through the two capabilities. On accessing an object pertaining to an application, if a second object pertaining to the other application is passed on to the latter, two other capabilities are added in the applications to protect access to the second object.

Abstract: The invention concerns an application programmer no longer responsible for managing access rights. the application code being independent of the protection in the chip card The capability-based access control consists, when an application (Aa). for example in a docking station. is given access to an object (Ob1) pertaining to the other application (Ab) in a chip card (CP), in creating two capabilities (Fa(Ob1). Fb(Ob1)) respectively in the applications, as objects. to protect all subsequent accesses to the object by filtering them through the two capabilities. On accessing (E1) an object (Ob1) pertaining to an application (Ab), if a second object (Ob2) pertaining to the other application (Ab) is passed on to the latter, two other capabilities (Fa(Ob2, Fb(Ob2)) are added (E2) in the applications to protect access to the second object.