8/5 question for the MS Exchange VSAPI aware folks out there. In
VSAPI, are scan engines implemented as DLLs (or similar shared
objects) that are loaded into Exchange's address space, specifically
the Information Store, or are they separete processes that
communicate with Exchange via pipes/sockets/etc ala Milter? I'd
"read the fucking documentation", but apparently MS doesn't make
that readily available to non-developer$ --Jon
\_ Developer$, developer$, developer$, developer$, developer$
developer$, developer$, developer$... --SweatyBallmer
\_ They are separate processes. -geek
\_ Try again:
Login: geek Name: Eugene Kim
Directory: /home/sequent/geek Shell: /csua/adm/bin/safesorry
Never logged in.
Mail forwarded to eek+geekfwd@ocf.berkeley.edu
\_ Jon, read this:
http://msexchangeteam.com/archive/2004/10/20/245157.aspx
...
Vendor Scanning DLL
This is a DLL provided by an anti-virus vendor written to the
VSAPI specification. The specification essentially states
the vendor must provide 3 interfaces: A startup function,
a scanning function, and a shutdown function. The Information
Store loads this DLL into the Information Store process. Upon
loading the DLL, the Information Store calls the startup
function provided by the vendor. As with any DLL running in a
process, the vendor can allocate memory, spawn new threads for
supporting reporting functionality, or initiate communication
to other processes on the system supporting the VSAPI engine.
\_ Dude, who the hell would ever read that? -average American |