Hi, Am I correct in understanding we are going to need a real rpc implementation to correctly support Plug and Play as well as Services, DCOM and SMB related stuff? I know the Wine DCOM and Service Code does everything over named pipes on the local system but I assume we want to do things "properly". Should we look at doing a mingw build of FreeDCE or the DEC-RPC? I am happy to try and help import any code if it will help.
Thanks Steven
__________________________________ Do you Yahoo!? Yahoo! Small Business - Try our new resources site! http://smallbusiness.yahoo.com/resources/
Steven Edwards wrote:
Hi, Am I correct in understanding we are going to need a real rpc implementation to correctly support Plug and Play as well as Services, DCOM and SMB related stuff? I know the Wine DCOM and Service Code does everything over named pipes on the local system but I assume we want to do things "properly". Should we look at doing a mingw build of FreeDCE or the DEC-RPC? I am happy to try and help import any code if it will help.
It may be a correct and safe pro tempore solution, considering how complex RPC is, but keep in mind that same node calls use LPC, to avoid RPC overhead. This again leads to implement LPC with correct semantics, which is a complex task too.
Emanuele
Steven Edwards wrote:
Hi, Am I correct in understanding we are going to need a real rpc implementation to correctly support Plug and Play as well as Services, DCOM and SMB related stuff? I know the Wine DCOM and Service Code does everything over named pipes on the local system but I assume we want to do things "properly". Should we look at doing a mingw build of FreeDCE or the DEC-RPC? I am happy to try and help import any code if it will help.
IMHO, adding missing features to WIDL and fixing resulting bugs in rpcrt4 is much more important right now. Access to remote machines, new transports (tcp, udp, http, etc.) and a dynamic endpoint mapper (aka rpcss) is not that important.
Regards, Eric
-
ea -
Eric Kohl -
Steven Edwards