Seite 1 von 1

BeitragVerfasst: Sa 14. Jun 2008, 08:08
Author: taz
I'm not CA "guru" (and as far as eMule programming - I'm probably not a "guru" of any peace of code), however :

I think there's a miss in some 0.49a mods with CA around collect spammer data -

it should be shifted from CChatSelector::ProcessMessage to CUpDownClient::ProcessChatMessage and CUpDownClient::ProcessMuleCommentPacket

focusing around SetSpammer(true) with an addition for empty str.


-- anyway this is the way I implemented it in my "mod generation" (aka "platform")

BeitragVerfasst: Sa 14. Jun 2008, 09:31
Author: WiZaRd
If you check the CVS then you will see that I changed that already... I didn't merge it but Dlarge and he doesn't know my code like I do Bild

BeitragVerfasst: Sa 14. Jun 2008, 09:53
Author: taz
If you check the CVS then you will see that I changed that already... I didn't merge it but Dlarge and he doesn't know my code like I do Bild


Now I see - however why the collection is dependent on thePrefs.IsAdvSpamfilterEnabled() ?

(it wasn't in the past, nor in the way I changed it)

BeitragVerfasst: Sa 14. Jun 2008, 10:02
Author: WiZaRd
I didn't check it in detail and I have a lot of changes here that I haven't checked in, yet... so it might already be solved Bild

BeitragVerfasst: Sa 14. Jun 2008, 11:26
Author: taz
I didn't check it in detail and I have a lot of changes here that I haven't checked in, yet... so it might already be solved Bild


If it's going to stay as is (i.e. corelated with SetSpammer(true)) it might be worth shifting it into SetSpammer - that way a single point to maintain ... Bild