There are many ways to use threads. Which is approriate for your particular application will depend upon what that application is. Unless you describe your application, all you will get is meaningless handwaving answers. It is impractical for anyone to describe all the ways they can be used so that you can pick the appropriate one. Besides, you almost certainly wouldn't be equipped to make that decision up front.

I see from one of your previous questions that you've already read the nearly useless perlthrtut and are still none the wiser. (Don't feel bad, very few will ever learn anything useful from that document.)

If you are seriously pursuing help with creating a multitasking solution to your problem, then you will need to describe that problem in some detail, and explain what you are hoping to achieve by multitasking it.

One last piece of advice: Write a non-multitasking version first. Once you have a working, single tasking solution, it will be far easier to explore multitasking and: a) verify that the addition of multitasking isn't causing incorreect results; b) get a feel for whether you are actually benefiting from the extra complexity involved.

Are there any documents you would recommend in place of perlthrtut ?

None that I have seen.

perlthrtut is little more that a verbose expansion of the threads pod. More reference than tutorial. All how and no why.

Imagine someone asking the question: "I want to bake a pie".

You could tell them about making pastry. You might mention the difference between savoury and sweet pastry. You could attempt to cover the need for a light touch and the affect of hand temperature upon pastry texture. You might mention blind baking. You might list some cooking temperature/time guidelines. You could talk about wet and dry fillings; and the need vent steam; and soggy crusts.

But unless you start out by asking them the type of pie they are wanting to bake; the kind of filling they envisage; and how many people they are hoping to serve; most all of that advice is just going to set them up for disappointment.

---

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."

You might learn something from an article I wrote about using Perl threads in little toy app:

http://www.perl.com/lpt/a/667

Personally I prefer to use fork and pipes for IPC when I'm doing parallel programming with Perl. Perl's threads are too slow and the problems using non-thread-safe XS modules are too painful.

-sam

Hello BU

Thanks for the Explanation.

i will abstarct out my project here.

SuperVault is a complete backup restore and disaster recovery solution. The solution is being implemented as a client server environment where in the client is the front end which is known as back up engine and the server is the back end which is made of a scalable distributed data storage system.


I deal with Test Harness of this product.Test Harness (TH) is a suite of tools (That is Customized)that helps us to perform functionality and performance testing on Super Vault solution. The suite helps the user to perform the following activities.

1) Creating test cases
2) Managing test cases
3) Managing test case collections
4) Executing test case collections
5) Generating test execution reports

Till now ,We are doing synchronous data transfer for sending and receiving acknowledgments for each block being sent.

But We need to have buffered asynchronous mode data transfer from now onwards.

But We need to have buffered asynchronous mode data transfer from now onwards.

Everthing you wrote prior to that line was 'sales pitch'. It tells us nothing about what help you need.

• But We need to have: Why? What are you hoping to gain?
• buffered: Buffered where? (At the client; at the server; both?) Buffered why? (To reduce communications bandwidth? To coalesce adjacent transmissions?
• asynchronous mode: "mode"?
• asynchronous ... data transfer: Why? What are you hoping to achieve?
  • Increase throughput?
  • Reduce server latency?
  • Improve client responses?
  • Speed up your testing cycles?
  • Saturation test your servers without requiring dozens of physical test clients?
  • Allow you to add the "asynchronous" keyword to your adverts so as to stack up better against your commercial rivals?
  • Avoid having to employ more testers?

Unless you can answer the questions above without asking your manager or mentor, you are probably the wrong person to be tackling the project.

And is that from now onwards, the now when you posted; or the now when I read it? :)

On a more serious note. If you are under pressure to try and complete this by some prescribed deadline, despite that you do not yet have a good idea how you are going to so, then you should seriously consider taking the project back to your management and telling them to ...

---

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."

Well you need to start with: perlthrtut.

If you've already read that, and you're still stuck, then ask further...