Number of sources problem when using the GUI protocol

[IrYoKu]

Hi,

I have developed a very simple client that displays current downloads in a superkaramba widget (a little application that lays in KDE desktop).

I show the number of sources for every download, and I am having troubles with that.

I am using the FileAddSource & FileRemoveSource messages to monitor the number of sources. Exactly, what I am doing is:

For every download set nSources = 0

Then, when receiving messages:
If a receive FileAddSource, then I increase nSources for that file.
If a receive FileRemoveSource, then I decrease nSources for that file.

The number of sources looks good at first (I compare it with the telnet interface output), but after a while the number of sources is less than it should, and after a looong time it ends up as a negative number.

I think that maybe I am missing something, so if someone can help me, I will appreciate it a lot. Some advices, things that I can check, etc.

Thanks,
IrYoKu

[su_blanc_]

Hi,

in the message opcode 52 FILE_INFO Core -> GUI, you have 2 fields file_active_sources (int) and file_all_sources (int).
If I were you, I would also use the message opcode 64 'InterestedInSources false' GUI -> Core (not to be flooded by the FileAddSource FileRemoveSource messages) when you have established the com with the Core.
To refresh the values you can use the message opcode 37 'GetFile_info (int)' GUI -> Core, from time to time.

Note that I never checked the accurracy of the values given by file_active_sources and file_all_sources.

hope that helps.

[IrYoKu]

Thanks for your reply

From protocol version 17 it seems that the file_active_sources & file_all_sources in the fileinfo message are always zeroed. A quote from g2gui protocol info:

[IrYoKu]

I have upgraded mldonkey to last version (2.5.30-4), and the problem of sources is there too... I don't think it's a problem of my client code, because it's doing really trivial things and I have revised it hours and hours, so or it's a concept problem (maybe I don't have understood well the protocol, specially the add and remove sources messages) or is a core problem.

And now after upgrading to last version, I have other problem, the core is not sending the updateAvailability message (opcode 9) anymore. Why? I searched through the change log and found nothing about this.

Come on guys help me, I am really stuck

[fabtar]

let''s try setting "good queue rank" to 6000, this settings helps a lot in my 2.5-16 ...only a try

[su_blanc_]

Hi,