Interoperability between DBus implementations on Windows

[Thiago Macieira]

Em Segunda-feira 26 Outubro 2009, às 09:17:42, você escreveu:
> >> DBusSharp implements an altogether different
> >> transport mechanism based on Windows named pipes [...] So should this
> >> named pipe transport then also be added to the dbus4win (and/or
> >> upstream) implementations?
> >
> > I doubt it. See my reply on the subject dated April 21 (Message-Id:
> > <200904211833.35416.thiago at kde.org>)
> 
> Yep, I remember that message. I wonder how well the "win" transport in
> DBusSharp actually works then? They don't seem to use it in their
> daemon implementation, Daemon.cs says: string addr =
> "tcp:host=localhost,port=12345";  and as far as I can see doesn't
> offer a way to change that. (Those parts have been commented out.) So
> probably the "win" (named pipe) transport in DBusSharp is/was just an
> experiment that didn't succeed that well? Anybody from DBusSharp here?

Probably.

Like I said, named pipes are a dead-end. They are not supported on Windows CE.
-- 
Thiago Macieira - thiago (AT) macieira.info - thiago (AT) kde.org
  Senior Product Manager - Nokia, Qt Development Frameworks
      PGP/GPG: 0x6EF45358; fingerprint:
      E067 918B B660 DBD1 105C  966C 33F5 F005 6EF4 5358
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part.
Url : http://lists.freedesktop.org/archives/dbus/attachments/20091026/3f7bdacd/attachment.pgp