Our single-threaded GUI app was freezing whenver we did dateabase
reads and it looked like the app had crashed. Therefore we threaded
the app and visual response significantly improved.
What alternatives are there to our problem
You had a problem, you solved it. Why are you looking for alternatives?
Because I like to know the pros and cons of possible
solutions. Especially considering the fact that mst said perl
threads sucked. Now, he did refuse to explain why, but he did mention
those other CPAN modules as alternatives. And I also made it clear
that my solution was potentially redundant/conflicting becuase Glib
already had threads
(Ps. Why, uniquely do you feel the need to ask your questions in
Big Bold Lettering?
Are they somehow more important than other peoples questions?)
Each of us is a fingerprint of God, dont superimpose your fingerprint
and its tendencies on mine.... or even waste your time in
criticism. But anyway, I like to take the semantic aspects of my posts
and use the visual layout to distinguish them.
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|
