[Pidgin] #1522: UPnP timeout period is ridiculously long
Pidgin
trac at pidgin.im
Sun Jan 4 11:08:35 EST 2009
#1522: UPnP timeout period is ridiculously long
----------------------------------------------+-----------------------------
Reporter: rgovostes | Owner: evands
Type: patch | Status: new
Milestone: | Component: libpurple
Version: 2.0.1 | Resolution:
Keywords: upnp timeout file transfer oscar |
----------------------------------------------+-----------------------------
Comment(by evands):
Ryan, I've attached the patch you sent me 7/5/08 in an email entitled
"libnatpmp take 1". You said:
> I'm attaching a preliminary diff for libnatpmp support. When you have
some time, would you be able to help me update the Makefile to include the
libnatpmp .c files (I have them in libpurple/libnatpmp)? Alternatively we
can use libnatpmp's Makefile to build the static library version and link
to it.[[BR]]
[[BR]]
> Sadly, my libpurple isn't compiling right now due to problems with
Jabber, so I can't tell if there are compile errors with my code. I ran
clang on it and looked through the results for syntax errors, and there
don't seem to be any.[[BR]]
[[BR]]
> I think it would useful if we could tie in with the runloop to not block
when we get the "try again" signal, but I don't know enough about
libpurple to imlpement this.[[BR]]
[[BR]]
> Since I don't have a NAT-PMP router, would you also like to be the first
guinea pig? :-)[[BR]]
[[BR]]
> UPnP support is harder, since libminiupnp doesn't have a 1:1 mapping as
libnatpmp did to nat-pmp.c. I'll get started on it this weekend, but there
are a few design choices. For instance, do we want to use a straight-
MiniUPnP implementation, or should we defer to libpurple implementations
when there's overlap? E.g. they both have XML parsers.
--
Ticket URL: <http://developer.pidgin.im/ticket/1522#comment:14>
Pidgin <http://pidgin.im>
Pidgin
More information about the Tracker
mailing list