well that is the first thing that i had asked .. but getting help from the current dev ( with there on work pressure) is the first risk.Infact i had made a simple script that would fire and compare but i could not get a replica in C++ and so couldn't compare.

The only way i think i can beat the current app is by doing things parallely.

Well i can fire max 20 query processes/Threads and get response from the app server parallely.If i can find a way to do comparison parallely i think i can win.That is why i thought of the queryBoss/queryWorker and compBoss/compWorker concept.The queryBoss would launch X no of queryWorkers and they start quering dequeing the query from the threaded queue.They also do the first level of comparison ( string compare of both the results).if this comp fails they dump the results in prod and test file and store the name of the files in a Global threaded Queue.The compBoss if blocking on this Global Threaded Queue containg file names.As soon as it is able to dequeue an object that is defined it launches X no of comp threads with Global Threaded Q's object as a parmeter.It enqueues the object again , one that it had dequeued to come out of its blocking state.Each compWorker dequeues the object and starts comparing the files

In reply to Re^20: Problem in Inter Process Communication by libvenus
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.