Hi! Those TThreads seem to have the main things I needed. I just used the ones "i Understood well" and kept adding more to my repetoire - now I pretty much love the FPC threading model. I'm not a thread hound either as my hint at multiplexors may suggest but it's pretty slick, and gets the job done "Git-r-dun" (B^)>
You can work them a few different ways and I'm not a threading king but I made a wrapper that does the fire and forget BUT my wrapper has an extra setting to stay WAIT until I say go... this allows me to get the fire and forget "initialisation" and then have posed at the ready. You can do this more atomically with call right in thread to pause, or whatever. There is a demo that comes with FPC that has two simple processes writing 1 and 2 to the screen. Believe it or not - I used that simple demo as the start of my FPC threads education/experimentation. I DO need to point out that in Linux, my interthread messaging system (like your IPC) works awesome but in windows I had to pick a different algorythm (less "slick" - and it worked - no exact reason other than I thnk in windows I get deadlocks maybe and not in Linux or Mac.) Instead of even driven "Thread done, pose for next go" In windows I made a queue of "finished" threads and worked it more like a fifo. (think web server with 20 idle threads for example waiting for work). In short - I do think it's slick enough for that AND I've had some success using the FPC "gui-less" stuff perfectly when dropping it into Lazarus projects (which one hopes for but when I see it work - I cheer) Where FPC is cheetah, Laz is the finicky cat: awesome when the final exe is compiled and purring away but I digress again. Jason P Sage - Jegas, LLC - 860-871-6691 - 9 West Road FL#1 - Ellington CT, 06029 This communication, including attachments, is for the exclusive use of addressee and may contain proprietary, confidential and/or privileged information. If you are not the intended recipient, any use, copying, disclosure, dissemination or distribution is strictly prohibited. If you are not the intended recipient, please notify the sender immediately by return e-mail, delete this communication and destroy all copies. -------- Original Message -------- Subject: Re: [Synalist] TIMAPSend - solutions for freezing From: Krzysztof <[email protected]> Date: Thu, May 12, 2011 3:59 pm To: Ararat Synapse <[email protected]> Do you mean that FPC threads can works in background and keep imap client connected to server? I always thought that they do what they have to do and end their action. How this works? Some kind of loop in Execute method which keep imap connection and listen for task from main thread? ------------------------------------------------------------------------------ Achieve unprecedented app performance and reliability What every C/C++ and Fortran developer should know. Learn how Intel has extended the reach of its next-generation tools to help boost performance applications - inlcuding clusters. http://p.sf.net/sfu/intel-dev2devmay_______________________________________________ synalist-public mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/synalist-public ------------------------------------------------------------------------------ Achieve unprecedented app performance and reliability What every C/C++ and Fortran developer should know. Learn how Intel has extended the reach of its next-generation tools to help boost performance applications - inlcuding clusters. http://p.sf.net/sfu/intel-dev2devmay _______________________________________________ synalist-public mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/synalist-public
