AXHook – 25-year-old COM bridging and 32/64-bit interop framework
AngryIgor · 2 points · 1 comments · 9 jam yang lalu · Open original
Comments
1 preview comments · loading full thread
Log in to use comments
Log in to h4cker, then connect Hacker News to publish comments.
ANAngryIgor9 jam yang lalu
COM surrogate and architecture bridging framework designed to solve 32-bit/64-bit COM interoperability and process isolation challenges. Originally developed over 25 years ago for high-stakes financial environments, AXHook provides a robust drop-in replacement/overload for `CoCreateInstance`.
This framework was originally developed around 25 years ago during the era of enterprise systems engineering to solve complex integration challenges—due mostly to 32 to 64 bits conversion back then, as well as attempts to make OLE containers more stable to crashes in components. Since then, the Windows operating system has evolved significantly; however, developers still face persistent hurdles and interest in running 32-bit and 64-bit COM components interchangeably, as well as seamlessly running in-process components out-of-process (or vice versa) to protect container applications from crashes.
Comments
1 preview comments · loading full threadLog in to h4cker, then connect Hacker News to publish comments.
COM surrogate and architecture bridging framework designed to solve 32-bit/64-bit COM interoperability and process isolation challenges. Originally developed over 25 years ago for high-stakes financial environments, AXHook provides a robust drop-in replacement/overload for `CoCreateInstance`. This framework was originally developed around 25 years ago during the era of enterprise systems engineering to solve complex integration challenges—due mostly to 32 to 64 bits conversion back then, as well as attempts to make OLE containers more stable to crashes in components. Since then, the Windows operating system has evolved significantly; however, developers still face persistent hurdles and interest in running 32-bit and 64-bit COM components interchangeably, as well as seamlessly running in-process components out-of-process (or vice versa) to protect container applications from crashes.