Yes. It is theoretically feasible. But you have to come bak to the question, what are you gaining (or hoping to gain) by going the route of create threads on the fly?

There are legitimate reasons for doing this, but it is an expensive process that adds complications, some of which can be extremely difficult to resolve. So before I would consider going this route, I would need to have good reasons for doing so, and on the basis of what you told us so far, I do not see that reason?

What are your reasons for thinking this is a good idea?

Also, it would be easier to advise you if you woudl describe more details of the processing you are doing. For example, you say you are querying clients, but what type of clients and what type of queries?

And the second part of your processing is "comparing"...but comparing what? This is a comaprison:

if( $x == $y ) { #do A } else { #do B }

but it certainly wouldn't be worth starting a new thread in order to perform that operation. However, if you are comparing several megabyts of data, it might make sense.

For better advise, you need to explain more of what you need to do. And for serious consideration of your architectural questions, you need to explain why you are thinking of implementing them that way.


Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.
"Science is about questioning the status quo. Questioning authority".
In the absence of evidence, opinion is indistinguishable from prejudice.
"Too many [] have been sedated by an oppressive environment of political correctness and risk aversion."

In reply to Re^9: Problem in Inter Process Communication by BrowserUk
in thread Problem in Inter Process Communication by libvenus

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":



  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.