[Linuxdcpp-team] [Branch ~dcplusplus-team/adchpp/trunk] Rev 524: Fix setting v6_only flag (has to be before binding)

2011-09-07 Thread noreply
revno: 524 committer: Jacek Sieka branch nick: adchpp timestamp: Wed 2011-09-07 22:33:37 +0200 message: Fix setting v6_only flag (has to be before binding) modified: adchpp/SocketManager.cpp -- lp:adchpp https://code.launchpad.net/

[Linuxdcpp-team] [Branch ~dcplusplus-team/dcplusplus/trunk] Rev 2606: url parser fixes

2011-09-07 Thread noreply
revno: 2606 committer: eMTee branch nick: dcplusplus timestamp: Wed 2011-09-07 20:31:43 +0200 message: url parser fixes modified: dcpp/Util.cpp -- lp:dcplusplus https://code.launchpad.net/~dcplusplus-team/dcplusplus/trunk Your tea

[Linuxdcpp-team] [Bug 309402] Re: ipv6 support

2011-09-07 Thread Big Muscle
Implementations are different. (See above) -- You received this bug notification because you are a member of Dcplusplus-team, which is a bug assignee. https://bugs.launchpad.net/bugs/309402 Title: ipv6 support Status in ADCH++: In Progress Status in DC++: In Progress Status in Linux DC++:

[Linuxdcpp-team] [Bug 309402] Re: ipv6 support

2011-09-07 Thread iceman50
afaik it's a bit different from the one implemented in StrongDC, the IPv6 in DC++ well if you have anyone with IPv6 IP's it would be nice to test in pure IPv6 mode so by all means if you can help us with that you can inquire in DCDev Public hub -- You received this bug notification because you ar

[Linuxdcpp-team] [Bug 309402] Re: ipv6 support

2011-09-07 Thread Tehnick
I just saw the commit: http://bazaar.launchpad.net/~dcplusplus- team/dcplusplus/trunk/revision/2605 So it looks like original DC++ already has IPv6 support. Does anybody tested it? Also I didn't understand yet is this the same realisation as in BM project or another one? -- You received this bu

[Linuxdcpp-team] [Bug 837544] Re: Handles trapped on closing socket

2011-09-07 Thread Pirre
the problem is not that the socket is not closed on a disconnect or the entity is removed, its the handle created by the application to manage the socket that is not freed after the socket is closed. and yes this will kill a hub, and even the complete OS as each OS is limmited in max handles (NT b