QThreadPool based on QMap(msecs) instead of QQueue
-
Hello,
To manage in parallel two identic QFiles, I wants to link one QThreadPool to one other remote QThreadPool.For an architecture using such coordination, I imagine to use timestamp+msecs to coordinate the two internal QThreadPool's QQueued stack (so in my case I would rather prefer a QMap<quint64 timestampmsecs, QThreadPoolThread> instead of Qt core QQueued<QThreadPoolThread> stack).
If such architecture is not theorically wrong, it means that i need to code my own version of some Qt core files.
Is that architecture initially wrong ? Or can I create my QMap-time based QThreadPool system instead of QQueue ?
(It's a casual development, it could be archaic)
Thank you. -
@coucougael94 Can you explain your use case? What is "remote QThreadPool"? How are these files related to your threads? "I wants to link one QThreadPool" - what does "link" mean here?
-
Thank for reply (excuse my irrelevant english)
My use case :
I want to manage two identic files. (it is not for a commercial usage).The exchange between computers will be made using tcp with serialized exchange of commands and datas.
"remote QThreadPool" I want for the two computers, the two same stack, each seconds the two same file, and the two same computation, so the two same QThreadPool.
How are these files related to your threads ?
Each threadpool serve only one file, each threads can change or read the file (each thread one by one i.e maxThreadCount=1)."i wants to link one QThreadPool" a tcp link to have the same stack of modifications between the pair of files using msecs to have two same pool's stack.
-
@coucougael94 Why do you need threads?
