I think that if we want to split daemon/client, telepathy is an eccelent option since we would basically do the same thing with an implementation of our own. So the question is: would it be a good idea to split aMSN2 in a client/daemon structure?
Based on what I see from the centerim project, a LOT of people use a similar functionality, where you can start centerim in the background and do things from the command line. This is very much like having a daemon and a client which is only command line. With the described structure we would be able to do more and do it better! About the DBus dependency, I think that the only place where it could really be an issue is for people having a server configuration: in desktop environments it is pretty much already required by some other app, whereas servers without an X server probably don't have it installed. Yet there are some other factors to consider: first of all, AFAIK it is not a big dependency, but something quite small. Also, do the most common distributions already include it in their server version? For instance do Red Hat, Suse, Ubuntu server include it by default? Because if it's there, then most of the users will already have met that dependecy requirement, making it pointless to worry about it. Also I don't think that a dependency on DBus is a dealbreaker for anyone, but maybe someone disagrees on that... Here's my 2¢ :) -- Stéphane ------------------------------------------------------------------------------ Sell apps to millions through the Intel(R) Atom(Tm) Developer Program Be part of this innovative community and reach millions of netbook users worldwide. Take advantage of special opportunities to increase revenue and speed time-to-market. Join now, and jumpstart your future. http://p.sf.net/sfu/intel-atom-d2d _______________________________________________ Amsn-devel mailing list Amsn-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/amsn-devel
