FiveTech Software tech support forums

Dear All,

Just want to share my experienced with xHarbour's MT.. I know everyone was (may not) disappointed.. but I gave up so count me in.. then I settled for background task..

I just want to point-out that there are alternative ways that some of you may already know..

My idea is create one.exe for the task one and two.exe for the task two.. both running on windows background or just minimized on start.. these programs use some-kinda-quorum file (.dbf/.ini) which checks the task completed/queued by the other.. they do that while main.exe operates normally by end-user.

My created apps.. generates reports by one.exe.. process data by two.exe.. while main.exe accepts user-inputs all at the same-time.. some-kinda-multithreading or whatever you called it.. the output was so pleasingly accepted..

Until MT on (x)Harbour matures.. Then I am willing to wait..

Just my 2 cents.

fraxzi wrote:Dear All,

Just want to share my experienced with xHarbour's MT.. I know everyone was (may not) disappointed.. but I gave up so count me in.. then I settled for background task..

Which problems did you encounter using MT, exactly?

EMG

Dear EMG,

One of the problem I encountered was (xHarbour) it frequently hang on Win7 x64.. with WinXP x86 end-user experienced the same.. which I cant trace the caused.
That was 5 years ago though.. I settled to background task and wasn't able to look back with MT since then..

But I always fallow threads here about MT and how it grows-up..

Frances,

fraxzi wrote:That was 5 years ago though..

I wonder if the situation has changed since then...

EMG

Hello,

The Harbour and xHarbour multithreading are similar only in name. They are different implementations.
To me it is not valid as such any experience with xHarbour multithreading because it is well known for a long time the xHarbour multithreaded not work as well than Harbour.


regards