Direct Connection?

[darkstrike]

Hey all!

Long time, no-post, but I've been lurking

I just had a curious question for the development of aMSN, sorry if it's been asked before! I'm a fan of aftermarket MSN clients, and I noticed the other day when exploring Pidgin's Release Notes that they had managed to implement direct connections with MSN so file transfers wouldn't be atrociously slow. I was curious if there was any way aMSN could implement something like that? They had based the feature on the code of fellow named Gábor Szuromi, and if he had allowed it, would it be difficult or possible for aMSN to implement code such as his to increase the speed of file transfers?

No rush, and I'm not trying to be one of those n00by people who says "WE ARE NEED THIS FEATURE, LOLZ DOIT NOW!!!" Just was curious if such a thing were possible! Hell, I'd work on it myself, but I have no coding experience whatsoever, sadly.

Cheers!
 - Darkstrike

[kakaroto]

humm... euhh... well... hi...
for your info, aMSN has had full file transfer speed using direct connections since 1995, so.. that makes it since 5 years ago.. we were the very first to have it, and apparently until recently, almost the only ones who had it.. so yeah, no need to add that feature since we've got it already!
On a side note, we have a good summer of code student working on refactoring the msnp2p stack to make it easier to use and maintain, this should be helpful to implement msnp2pv2 support which would allow us to enable MSNP18 protocol support... If there's something wrong/missing with the p2p stack, we'll find it, but as far as I know, it works quite well already.

[Fabioamd87]

aMSN has had full file transfer speed using direct connections since 1995, so.. that makes it since 5 years ago..

did you mean 2005?

[kakaroto]

yes, 2005, hehe

[darkstrike]

humm... euhh... well... hi...
for your info, aMSN has had full file transfer speed using direct connections since 1995, so.. that makes it since 5 years ago.. we were the very first to have it, and apparently until recently, almost the only ones who had it.. so yeah, no need to add that feature since we've got it already!
On a side note, we have a good summer of code student working on refactoring the msnp2p stack to make it easier to use and maintain, this should be helpful to implement msnp2pv2 support which would allow us to enable MSNP18 protocol support... If there's something wrong/missing with the p2p stack, we'll find it, but as far as I know, it works quite well already.

Whoops! I hadn't noticed this reply...sorry for the late response Kakaroto ! I didn't know aMSN supported direct connections, that's great! I've just noticed from time to time that my file transfers seem very slow, and I know it's not my friends or I's internet connections, because when using WLM or the newest version of Pidgin, they go WAY faster...not sure if it's a setting, then, that I have selected in aMSN or not. I'll have to take a look.

MSNP18 would be great, new features and all! On a side note, is there any more work being done on getting Farsight to meet the current protocol requirements to get voice audio working again?

[alexandernst]

Farsight is not the problem, but msnp2p. vivia is currently working on it, so be patient.

[kakaroto]

Humm, well, I'm not sure why it wouldn't work, as far as I know, direct transfers work and have always been working.. although some people did complain about DC not working for them even if they had their ports properly forwarded in their routers... anyways, we've rewritten (Vivia did) the whole MSNP2P stack to make it much better, and vivia has rewritten the direct connection code, so if you want to test that, and if you notice a bug, feel free to report it, now's the time to fix all the new bugs introduced by this rewrite.
It is currently on a separate branch of SVN, but it will soon be merged into the SVN trunk.

[ElCynico]

Does the new MSNP2P bring any new features apart from (functional) MSNP18? I'd enjoy a multiple-points-of-presence while using Bitlbee through UNIX Shell & Irssi and aMSN.

[alexandernst]

well...msnp18 is exactly that! multiple-point-of-presence, and some more features.

[darkstrike]

Humm, well, I'm not sure why it wouldn't work, as far as I know, direct transfers work and have always been working.. although some people did complain about DC not working for them even if they had their ports properly forwarded in their routers... anyways, we've rewritten (Vivia did) the whole MSNP2P stack to make it much better, and vivia has rewritten the direct connection code, so if you want to test that, and if you notice a bug, feel free to report it, now's the time to fix all the new bugs introduced by this rewrite.
It is currently on a separate branch of SVN, but it will soon be merged into the SVN trunk.

I'm bringing back an older topic, I know, but I was curious if this has been merged into the SVN trunk as of yet?

[BW]

Hi darkstrike,

'til now it's still only in the separate branch and not merged

[vivia]

Hi,

The refactoring is done on a separate branch. You can safely use it, but it currently contains some memory leaks so it needs a cleanup. No other issues apart from that. It's on https://amsn.svn.sf.net/svnroot/amsn/branches/p2p . I just haven't found the time to do that cleanup yet, being very busy with university.

However, I noticed that the latest versions of Windows Live Messenger have one slight change in the way they negotiate about the direct connection. If you send a file and your ports are well-configured, it will go fast. If you receive a file, it will go slow even if your ports are well-configured. I will investigate that later.