Le jeu 05/06/2003 � 17:17, Mirar a �crit : > > So one reason more for GUI/core separation: > > 3. core can be distant (as with MLDonkey) > > Yup. And possibly a few more reasons: > > o) core can (right?) be made not dependant on GTK, and thus run on > more obscure systems if someone feels like it. > o) separating can allow for other flavors of both GUI and core, > independantly. > > I'm not sure what needs to be done for the separation. It might be a > matter of just transporting what's in gnet.h? In order to be more readable, I would be great if the files were splitted into 2 directories: a "gui" one and a "core" one. We could do it as soon as the latest version is released (soon I assume).
> Are there any really useful RPC libraries that can be used for this > kind of work, or do we (you) need to make up an inter-client protocol? If we were in a object world, I would choose a CORBA bridge. (By the way, why didn't you use C++ ?) I already used the XML-RPC protocole in the Python world. But to still respect the efficiency of gtk-gnutella, maybe we could use directly a TCP connection. The GUI protocol of MLDonkey already use it (see http://royale.zerezo.com/jmoule/interface_protocol.txt). The question is do we use our own protocol or do we use a part of the MLDonkey one ? J�r�me ------------------------------------------------------- This SF.net email is sponsored by: Etnus, makers of TotalView, The best thread debugger on the planet. Designed with thread debugging features you've never dreamed of, try TotalView 6 free at www.etnus.com. _______________________________________________ Gtk-gnutella-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/gtk-gnutella-devel
