<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=ISO-8859-1">
</head>
<body text="#000000" bgcolor="#ffffff">
Hello D-Bus people!<br>
<br>
I have started working on Pontarius 0.1, a set of free software
media server programs. [1]Pontarius will build services on top of
the [2]Extended Personal Media Network (XPMN) architecture, as
defined by Dirk Meyer. We will have a server program that will
transfer resources end-to-end encrypted over XMPP. I also want some
kind of client that can access these resources at the request of
other applications. So naturally I'm considering using D-Bus.<br>
<br>
Now, it would be great if the media accessor client could be <i>interoperable</i>
in that I can use the same client code across all platforms
(supporting the Python programming language) and <i>understandable</i>
in that it has a simple API that is easy to use to access media
assets. My idea (having close to zero experience of D-Bus) is to
expose my client's through D-Bus for GNU/Linux. I assume I should
separate the D-Bus part of my application from the rest of my
client's logic so that it doesn't require D-Bus?<br>
<br>
What would you do for Windows? Would the Windows port for D-Bus be a
good choice for my application? Or would implementing an OLE/COM
wrapper talking directly to the application be a better way to go?<br>
<br>
Any particular things to take into consideration for Mac OS?<br>
<br>
Any comments are welcome!<br>
<br>
Thanks!<br>
<br>
[1]: <a class="moz-txt-link-freetext" href="http://www.pontarius.org/">http://www.pontarius.org/</a><br>
[2]: <a class="moz-txt-link-freetext" href="http://elib.suub.uni-bremen.de/diss/docs/00011878.pdf">http://elib.suub.uni-bremen.de/diss/docs/00011878.pdf</a><br>
<br>
Warm regards,<br>
Jon Kristensen<br>
</body>
</html>