Overview
Examples
Screenshots
Comparisons
Applications
Download
Documentation
Tutorials
Bazaar
Status & Roadmap
FAQ
Authors & License
Forums
Funding Ultimate++
Search on this site
Search in forums












SourceForge.net Logo
Home » U++ Library support » U++ MT-multithreading and servers » what about WorkQueue : public CoWork
Re: changed CoWork and derived WorkQueue [message #25064 is a reply to message #25051] Tue, 09 February 2010 15:14 Go to previous messageGo to previous message
kohait00 is currently offline  kohait00
Messages: 939
Registered: July 2009
Location: Germany
Experienced Contributor
well, maybe it's because *I* have too little MT experience, i am a bit of a rookie on that indeed, still learning.

my situation was basicly that i wanted to keep the gui responsive (old stuff) offloading work (i realize that CoWork is mainly a loop parallelizer, for independant work). but as soon as the offloaded work is kind of depandant on each other or the order of execution, you only have the possibility to either PostCallback the work using the GUI thread (which for large work affects GUI respnsiiveness) or to use a 1-thread-workqueue, which executes in background in order of comits. both solutions *are* a WorkQueue, even PostCallback. With current CoWork this is *not* possible. for stated reason: CoWork is "only" a loop parallelizer..not a work scheduler. with the given changes, one could flexibilize that.

anyhow..i wont push that, dont feel bothered. you decide. i am working with the modified CoWork, and it seems to me relatively more fluent to post to WorkQueue (1 trhead CoWork) than to a threadpool CoWork.
 
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Previous Topic: DnD hangs in MT Refresh()ing
Next Topic: Linux MT problems with time functions
Goto Forum:
  


Current Time: Thu Aug 28 16:10:02 CEST 2025

Total time taken to generate the page: 0.00997 seconds