Quoting "=?iso-8859-2?Q?Tom=E1=B9=20Mudru=F2ka?=" <har...@email.cz> from ml.softs.gtk-gnutella.devel: :well it does matter on what you )developers( are preffering. i hope user will be :unaffected by selection of upnp library... anyway libminiupnp depends on glib :(only!), gupnp-igd depends on gnupnp, glib, python (!!!) and few more packages... :so i guess that libminiupnp is still more lightweight solution than using :gupnp-igd. i also guess that gtk-gnutella itself have well written code for :network communication, which can be probably used to communicate with upnp igd :service without need of any 3rd party libraries (you just need to read how UPnP :works...).
The problem of implementing UPnP in gtk-gnutella is that, apart from the task of implementing the low-level UPnP layer (or finding a good library with a proper API), you have to handle complex use-case scenarii: * Application crash. * Multiple instances. * Live configuration changes. * Network device resets. This requires many hours of work, too many for me currently anyway. And I don't need that and have to UPnP device to test it, which considerably lowers the priority of the task. I already have 3+ years worth of "TODO" tasks in my backlog. :-( Raphael ------------------------------------------------------------------------------ This SF.net email is sponsored by Sprint What will you do first with EVO, the first 4G phone? Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first _______________________________________________ gtk-gnutella-devel mailing list gtk-gnutella-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/gtk-gnutella-devel
