BREAK EVERYTHING; spread out online stuff into more classes (Credentials, OnlineDatabase, Tracker); stupid attempt to fix TvShow relations by using the title as a connection, they should be partially moved to OnlineDatabase::Entry and applied to the TvShow;
shit compiles again;
disable franchise creation, auto emit onlinesync finished and fix error in TvShowRelation constructor, so things start up again;
BROKEN: started implementing OnlineSync;
BROKEN: continue implementing OnlineSync; use more const functions;
partly impl tracker updating, but don't integrate it into the usage flow, yet
BROKEN CODE: started db-fetching code; actually read the credentials;
check if a show needs a fetch and cancel fetching if it doesn't;
make OnlineSync a thread and start it when something is added to it's lists
disabled Otsdb::Thread based code;
pass BaseConfig instead of absolute mal path to OnlineSync to stay more Service independant;
WON'T_COMPILE: fix some bugs with maltracker, next thing to do is franchises and migration of old data;
attempt migration of old remoteId data
changed the data, so remoteIds are matched to service-identifiers, TODO implement functions for new data struct
document the use of this class
BROKEN: started implementing franchise references
make most Franchise stuff kindof logical again, still got migrations to do
STILL NOT TESTED: added migrations for old Franchise Relations data;
fix writing to properly close onlinesyncData arrays
SEVERE CRIMES AGAINS MULTI-THREADING AND NETWORKING LAWS and everything that is sane to do. Dunno, but it seems to work this way oh gawd:
Added TimeLock to OnlineCredentials that locks the thread, so that only 1 curl-client is returned every second.
Block the OnlineSync Thread from finishing when... ehhh... it didn't finish yet? I've got no idead how signaling works,
apperantly not synchronous in-emitting-thread, otherwise I wouldn't have to block the thread?