Skip to content

Commit

Permalink
Update 2._DCOM.md
Browse files Browse the repository at this point in the history
  • Loading branch information
Robert Ostwald committed Apr 6, 2021
1 parent 3e36b09 commit 619de91
Showing 1 changed file with 2 additions and 2 deletions.
4 changes: 2 additions & 2 deletions documentation/1._Introduction_to_OPC/2._DCOM.md
Original file line number Diff line number Diff line change
Expand Up @@ -28,7 +28,7 @@ DCOM (Distributed COM) has existed ever since Windows NT 4.0 came into existence
Two important questions are: how does the client get the first pointer to the interface of a server? How does the client launch a server?


# Bild
![OPC-Classic-SDK](https://github.com/SoftingIndustrial/OPC-Classic-SDK/raw/main/documentation_pics/CMN_Intro_001_1.jpg)

The client calls the function CoGetClassObject(). This function is provided by the operating system in the DLL ole32. The following parameters, among others, are transferred to the function:

Expand Down Expand Up @@ -69,4 +69,4 @@ The safety requirements are bi-directional.
Security can be achieved in two ways:

- Information on security aspects is contained in the registry. This works for components that are either not aware of security mechanisms or do not use them. It can be changed using DCOMcnfg. This is known as declarative security.
- Through the introduction of DCOM, a series of program-specific methods are available with which widely varying security features can be achieved. This is known as programmatic security.
- Through the introduction of DCOM, a series of program-specific methods are available with which widely varying security features can be achieved. This is known as programmatic security.

0 comments on commit 619de91

Please sign in to comment.