Can't send new patch's

[ivan386]

I can't send new patch's until other will be accepted or declined. To many changes done in my code.

Next patch will be ut_pex (bt source exchange).

[cyko_01]

I know you are working hard and submitting a lot of code but you need to make sure that you are adding features that the community wants (especially major features like btpex) and implement/integrate them properly. Also, we are not interested in quick-n-dirty workarounds for bugs.

[kevogod]

[mojo85]

Is Ryo okay, haven't seen him posting as of late. BTW ut_pex is a major addition ... it is bt peer exchange and ut_pex is what the majority of clients support ... Vuze/ Azureus has there own implementation which is the alternative ... but I say go with the majority when it comes to sources.

Hey Ivan I'll test run your additions and see how stable they are ... in the meantime keep posting your updates and patches, I'm sure Wildcard or Ryo or whomever has a chance will place it in the common source. Please post the ut_pex code as well I would like to test this as well, quite a major improvement on Shareaza's BT part.

[ivan386]

[old_death]

Hey, ivan, this has been missed for a long time! Many thanks for the patch, it should make Shareaza much more efficient when interacting with other BT clients in the swarm...

[mojo85]

I can't seem to build this with the changes you suggested, m_nUtMetadataSize is undeclared how should I proceed?

[mojo85]

Well I changed the variable assignment name for the previous m_dUtMetadataSize to m_nUtMetadatSize ... hope that is what you meant ... commencing testing.

[ivan386]

1 Rename all of m_dUtMetadataID to m_nUtMetadataID
2 Rename all of m_dUtMetadataSize to m_nUtMetadataSize