Homeopathy Vs Ayurveda

Ayurveda and Homeopathy are two streams of natural remedies that are the mainstay of alternative as well as holistic medicine. Homeopathic medicine is known more for its use of 'atomized or potential' remedies. The remedial measures are well developed but there is specific lack of holistic approach toward lifestyle and dietary factors.

Ayurveda And Homeopathy - The Basic Concepts:
There is some basic difference in the principles of ayurvedic medicine and homeopathic medicine. Though the fundamental principle of homeopathic medicine is utilized in ayurvedic medicine many times but this approach is still originally and innovatively used in homeopathy.

Homeopathy is based on the principle 'similia simillibus currentaer'. It simply means that similar medicine treats similar disorders. Each homeopathic remedy possesses its own unique profile of symptoms. It is like that every homeopathic remedy is a character with individual features. A homeopathic doctor should be able to be as familiar with these remedies just like a family member or a friend.

In the ayurvedic medicine, there are six basic approaches with which food, medicine and lifestyle can be utilized to deal with various disorders. The Homeopathic approach of treating the similar with similar is just one among them.

Ayurveda And Homeopathy - The Remedial Measures:
There is tremendous similarity in the various remedies of both ayurveda and homeopathy. Most of the remedies are derived from plants, minerals and animal kingdom. Many of the names are same in both systems of natural remedies.

Ayurveda And Homeopathy - What is the Form Of Medicine and how are the Remedies Prepared?
Ayurvedic medicine is mostly crude. Herbs and minerals are used in crude form after their purification and after enhancing their bio availability.
In Homeopathy, remedies are used in potentate and subtle form. There are various potencies of remedies ranging from mother tincture or zero to one million. Mother tincture is the basic formulation where crude herb or mineral is dissolved in alcohol.

Ad: Click Here to learn about an Effortless Ayurvedic Beauty Program.!





Video of homeopathy on Youtube:


Video of ayurveda on Youtube:

Overview of Threads

A thread is an encapsulation of the flow of control in a program. Most people are used to writing single-threaded programs - that is, programs that only execute one path through their code "at a time". Multi-threaded programs may have several threads running through
different code paths "simultaneously".
A thread is similar to the sequential programs: a single thread also has a beginning, an end, a sequence, and at any given time during the run time of the thread there is a single point of execution. However, a thread itself is not a program--it cannot run on its own--but runs within a program.

Why use threads?
Threads should not alter the semantics of a program. They simply change the timing of operations. As a result, they are almost always used as an elegant solution to performance related problems. Here are some examples of situations where you might use threads :
* Doing lengthy processing: When a windows application is calculating it cannot process any more messages. As a result, the display cannot be updated.
* Doing background processing: Some tasks may not be time critical, but need to execute continuously.
* Doing I/O work: I/O to disk or to network can have unpredictable delays. Threads allow you to ensure that I/O latency does not delay unrelated parts of your application.

In the program, some operations incur a potentially large delay or CPU hogging, but this delay or CPU usage is unacceptable for other operations; they need to be serviced now.
* Making use of multiprocessor systems: You can't expect one application with only one thread to make use of two or more processors! Chapter 3 explains this in more detail.
* Efficient time sharing: Using thread and process priorities, you can ensure that everyone gets a fair allocation of CPU time.

Similarities between process and threads :
* Like processes threads share CPU and only one thread active (running) at a time.
* Like processes, threads within a processes, threads within a processes execute sequentially.
* Like processes, thread can create children.
* And like process, if one thread is blocked, another thread can run.

Differences between process and threads :
* Unlike processes, threads are not independent of one another.
* Unlike processes, all threads can access every address in the task.
* Unlike processes, thread are design to assist one other. Note that processes might or might not assist one another because processes may originate from different users.