Abstract: Leveraging an established authenticated session in obtaining authentication to a client application includes receiving a request for access to a client application requiring authentication of a requestor and determining whether there exist characteristics of leverageable authentications corresponding to established sessions having an authenticated state at a time of the determination. When the determination reveals characteristics of at least one leverageable authentication corresponding to an established session, and attempt is made to obtain access for the requestor to the client application based on the at least one leverageable authentication, and the requestor is provided with a notification related to the 1 attempt to obtain access for the requestor to the client application.

Abstract: Leveraging an established authenticated session in obtaining authentication to a client application includes receiving a request for access to a client application requiring authentication of a requestor and determining whether there exist characteristics of leverageable authentications corresponding to established sessions having an authenticated state at a time of the determination. When the determination reveals characteristics of at least one leverageable authentication corresponding to an established session, and attempt is made to obtain access for the requestor to the client application based on the at least one leverageable authentication, and the requestor is provided with a notification related to the 1 attempt to obtain access for the requestor to the client application.

Abstract: Leveraging an established authenticated session in obtaining authentication to a client application includes receiving a request for access to a client application requiring authentication of a requestor and determining whether there exist characteristics of leverageable authentications corresponding to established sessions having an authenticated state at a time of the determination. When the determination reveals characteristics of at least one leverageable authentication corresponding to an established session, and attempt is made to obtain access for the requestor to the client application based on the at least one leverageable authentication, and the requestor is provided with a notification related to the 1 attempt to obtain access for the requestor to the client application.

Abstract: Leveraging an established authenticated session in obtaining authentication to a client application includes receiving a request for access to a client application requiring authentication of a requestor and determining whether there exist characteristics of leverageable authentications corresponding to established sessions having an authenticated state at a time of the determination. When the determination reveals characteristics of at least one leverageable authentication corresponding to an established session, and attempt is made to obtain access for the requester to the client application based on the at least one leverageable authentication, and the requestor is provided with a notification related to the attempt to obtain access for the requester to the client application.

Abstract: A code module is loaded in-process or out-of-process depending on metadata. The code module implements a service and the metadata is associated with the service. The metadata also indicates whether the code module is to be loaded in-process or out-of-process. A request for a service object provided by the service is received from a service requestor. The metadata is examined to determine whether the code module is to be loaded in-process or out-of-process and, when the metadata indicates the code module is to be loaded in-process, the code module is loaded into the process of the service requester. When the metadata indicates the code module is to be loaded out-of-process, the code module is loaded into a host process separate from the process of the service requester. The requested service object is instantiated using the loaded code module and the service requestor is enabled to access the instantiated service object.

Abstract: An object is developed using an operating system neutral application programming interface (API). The object is compiled for a designated operating system that includes native objects an supports an API for accessing native objects of the operating system. The compiled object includes logic code, a native object interop for accessing the logic code using the API for accessing native objects of the operating system, and a platform-neutral interop for accessing the logic code using the operating system neutral API.

Abstract: Services having associated metadata meeting particular criteria can be discovered. One or more services are stored. The services provide service objects to service requesters. Service requestors include compiled code and the service objects include compiled code that is linked to the compiled code of a service requester at runtime and that is executable by the compiled code of the service requestor. A metadata file is associated with each one of the services. A query message is received and includes a search query specifying particular criteria. At least some of the metadata files are searched to determine if one or more of the metadata files contain metadata that matches the particular criteria. When at least one of the metadata files contains metadata matching the particular criteria, the service associated with the metadata file is identified.