| pblais@odstrategies.org 2006-06-19, 7:55 am |
| Launching threads very quickly back to back seems to cause more
problems than if you make sure you always wait a short period of time
between them. That said I have two applications that have the
threading problem. The message box problem that seems to help with the
Capesoft tool I'm not sure about and in my cases I don't have many
messages boxes. I have traced all the problems and it's in the
threading system that shares between the threads. Soft Velocity fixed
right in 6.0. There is no true workaround possible.
The first app I added a delay between thread launches. This was a
server application that processed requests on a new thread. It still
has some problems but it's more like a w ly shutdown / startup. It's
been running since CW 4.0 and was improved a bit in 5.0. I know it
could be fixed in 6.0 because after all this time I understand the
threading problems it has.
The second application could not be fixed so we redesigned it to use
fewer threads and to share a threaded process. So in that way we
reduced the number of threads required and so solved the problem. I am
in the process of converting that app to 6.3 now for it's next major
release. This is a very large application with more than 20 DLL's. I
don't expect it to be a difficult conversion, just a lot of work.
While the 6.0 conversion presents some changes, they are not hard if
you followed the rules under 5.5. I would be hard pressed to convert
all my 5.5 apps to 6.3 as some are not billable. Apps with a future
should be converted. Fixing design and DCT issues before the
conversion can make it go easier. Doing both at the same time isn't
pretty. Get a good source code compare tool like Beyond Compare and
you can save a lot of time verifying and validating. I would test a
converted release with the same feature set then set out to add more
of the 6.0 features once you have done that. By all means fix DCT
issues first. The worst design problems are mostly dictionary design
flaws.
On 12 Jun 2006 12:36:58 -0400, Guest 7 wrote:
>I was wondering if there is any updated information on the dreaded Threading
>Error that manifests itself with Clarion 5.5?
---------------------------------------
Paul Blais - Hayes, Virginia
|