Re: interprocess communciation

The document in the link below is for desktop Windows. WinCE does not have
named pipes or mailslots. I don't think it has DDE either but I'm not sure.

DCOM (RPC) is only available on some WinCE images since it's an optional
component, and it's an expensive component (+500KB) at that so I would avoid
it if at all possible.

CE has a light-weight message queuing mechanism that is unique to it --
check out CreateMsgQueue and related APIs.

If you are doing something with a traditional client-server approach (even
if client & server are running on the same machine), then you may consider
writing a service DLL for services.exe. Check out
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnce50/html/implement_network_service.asp?frame=true.

--
John Spaith
Software Design Engineer, Windows CE
Microsoft Corporation

Check out the new CE Networking Team Blog at http://blogs.msdn.com/cenet/.

This posting is provided "AS IS" with no warranties, and confers no rights.
You assume all risk for your use. © 2003 Microsoft Corporation. All rights
reserved.

"sonu" <sonuthomas@xxxxxxxxx> wrote in message
news:1119865208.157737.33180@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
> Hi,
> the documentation is vaguely telling about the various interprocess
> synchronisation mechanisms in windows ce.
> Do we have any mechanisms other than the following
> 1) Memory mapped files
> using api's like createfilemap
> 2) Message Queuing
> it again have 2 flavours
> a) using sendmessage and getmessage
> b) WM_COPYDATA
> 3) Mailslots
> i have read the complete documentation about the above two and a lot
> of articles also.
> i heard that we have various other mechanisms from the article
> http://support.microsoft.com/kb/q95900/ which just mentions
> about named pipes ,OLE,windows socket,RPC,NETBIOS,DDE.
> can anyone tell me how the above mechanisms can be used or any
> articles describing about them.
> It would be really appreciated if any fruitful reply comes.
>
>
> Thanking you,
>
> with regards
> Sonu Thomas
>


.

Relevant Pages

  • interprocess communciation
    ... synchronisation mechanisms in windows ce. ... Do we have any mechanisms other than the following ... i have read the complete documentation about the above two and a lot ... articles describing about them. ...
    (microsoft.public.windowsce.platbuilder)
  • interprocess communciation
    ... synchronisation mechanisms in windows ce. ... Do we have any mechanisms other than the following ... i have read the complete documentation about the above two and a lot ... articles describing about them. ...
    (microsoft.public.windowsce.platbuilder)
  • Re: Executable enty points incorrectly documented
    ... I was speaking about Windows SDK not MSDN Library entirely, but even if Windows SDK conatins C/C++ documentation I believe that main/WinMain belong to C/C++ documentation rather than Windows API documentation. ... It's correct about the default entry point names used by the linker and also correct about what those entry points call and because this is the ...
    (microsoft.public.win32.programmer.kernel)
  • Re: ping Purl Gurl? Beginner Level Perl
    ... This is a good short one page article on perl core buffering, ... a lot of documentation amounted to nothing ... more than tirades about how bad Windows is as an operating system. ...
    (alt.usage.english)
  • Re: installing freebsd on windows
    ... windows vista runs well too on overmuscled hardware. ... Why do I have to Google the info? ... So you're trying to say that all local documentation is useless ... recommending that I do business with them again? ...
    (freebsd-questions)