Have you added the unknowns that I posted in des db update request thread? If yes we could use this ones for testing.
All unknowns from past days that have added to the server db have been populated. Older unknowns of the past year have populated too, as far as they have been added to server db too. But this only happens on first populate run after sw start, after that it doens't. During the first run in right bottom corner the processing picture/info requests counted down from 5000 to 0 (all requests done). During run two nothing happened in this area. This is different to V4 in which the requests were counted down again. In V4 in during both runs there is an increase in www comunication. In V5 this only happens during the first run of populate.
Just remember although no new details are available to downloaded to local db a check between local db and server db will perform traffic as sw has to sent requests and the server has to generate answers.
like this (extremely simplified)
SW to server: do you have details on this hex?
Server to SW: no. or yes: this are the details.
SW to server: do you have details on this hex?
an so on.
In V5 during second, third and so on run there is no increase caused by this comunication detectable. That's why I'm thiking that there is no actual comunication. During first run there is this typical increase of com. In V4 it was on each run of populate functionality. In V5 it's like: I've checked this hex, there is no detail on server so I don't have to check this hex again, but this would be a very false conclusion which makes the populate functionality absolutely useless for users that are running their boxes 24-7.
Today morning the populate function was dead for a couple of hours. I clicked on populate in MyLog window but absolutely nothing happened. After few hours it were accessable again, but no increase in traffic.
In my opinion if you select "alltime" in the list options and you run the populate function again, the sw shall go thru all unknown hex and request them from server again. Why? Maybe the infos have been added in the meantime. How can you get details to unknown hex codes if the software refuses to go thru all unkonws again. Maybe it is working with new unknonws in the list, but what is with older unknonws were the details are added a couple of days or even month later.
With V4 I did my db requests that way:
1st run populate (If I do the unknowns of Tuesday on Wednesday evening)
2nd run populate again to be shure that MyLog was update
3rd create and send new report for the day (in this case Tuesday)
4th do the requests.
This way all already updated unknowns have been updated.
If I try to do the same procedure on thursday eveving to process the unknowns of Wednesday, as in V5 populate does work as it should only one time after restart.
Hope that helps a bit.
Ingo
