[ros-kernel] Re: WINE porting templates

[KJK::Hyperion]

At 17.57 15/10/2003, you wrote:
>>User32 and gdi32 are likely to be a problem as the bulk of our 
>>implementation is in kernel mode win32k.sys.
>More problems will be caused by advapi32 and rpcrt4 because ReactOS will 
>use LPC instead of Unix-Sockets for local IPC.

naw. The "fork" will be limited to writing different RPC drivers for the 
ncalrpc transport. ncacn_ip_tcp and ncadg_ip_udp will make us face a 
choice, though: performance or portability? the Microsoft drivers (it's a 
documented fact) talk to the network drivers directly, because Winsock was 
deemed to add too much overhead to the already fatty DCE RPC protocol. But 
if we use Winsock, we'd be able to share 100% of the code with Wine (we 
have an advantage over Microsoft, though - custom builds will be a strong 
point for ReactOS, and a "fake" Winsock DLL supporting just TCP and UDP 
could be used, if the user desires so, in place of the true one, achieving 
the best performance - with 100% compatibility - for people that don't need 
to run odd network protocols)