[ros-kernel] SbApiPort

Aliberti Emanuele ea at iol.it
Tue Feb 3 00:30:28 CET 2004


\Windows\SbApiPort
\PSXSS\SbApiPort

What are they for? These ports are created by environment subsystem 
servers (subsystem=3: CSRSS.EXE+*SRV.DLL; subsystem=7: PSXSS.EXE) 
immediately *before* connecting to the SM's \SmApiPort port to 
initialize a "session" (session as in *S*M). In the connect data sent to 
the SM by issuing a call to NtConnectPort("\\SmApiPort"), the server 
process declares the name of its Sb (Session Beginning?) port and what 
subsystem it will emulate. In turn, the SM calls back the subsystem 
server by connecting to its registered SbApiPort. SmApiPort API # 1 is 
there to complete this session establishment process by the server side.

Should we implement this SM behaviour? What are the cons in putting the 
code to perform these operations in a separate DLL (say SMDLL.DLL)?


More information about the Ros-kernel mailing list