@kas ob
First, the only Standard Interrupt on Windows is INT 3. It will be handled as/for Debug reason. This Interrupt is addressed into the GDT, and IDT Table (that is an Operating System Issue). I don't want go into the depth with this, because it will cover more things, that you don't understand.
Again, you need to create a Instance of a
Exception Class to "stack up" the
Exception.
Each
Exception (class) need then stack Prolog, and Epilog.
The Prolog is for clean "build stack", the Epilog is for clean "destroy stack". This is a very import memory thing, because each
Exception "can" have Parameters like .Create(42); or .Create('foo'); or .Create('foo','fufu',42); or simply .Create;
Exception's will be "raise" with: raise EExceptionClass.Create; or EExceptionClass.Create(42); ...
Again, you can not do simply raise EExceptionClass.MyExcept; because raise point then into memory where "not" your code have
access, and Windows will prompt you with MAV's.
Second, Microsoft Windows uses very often
COM+ (Component Object Model) things.
That is based on the Terminal Server Services, and/or the Remote
Access Services (RD Remote Desktop).
This services are for centralized the maintain flow of Enterprise/Corporation's firms Computerdesk.
To hold the traffic and latency of Applications for this Services on a low Level, Microsoft plays a little bit with it's own technologies.
As such, they transmit data in form of image data, and plain text (like numbers that describe, what Function is to call on the counter part of the connection. This is then from Server to Client, and Client to Server.
- You can take a look onto the RPC Protocol, and it's implementation (Tools).
- You will realize that many things are based on numbers
RPC is a very old Protocol from Unix Workstations, and Unix Servers back into the 1970th.
Zitat
Baum-Darstellung
