The real deal is strange and sometimes embarrassing, so we decided to get to the bottom of it. What is it that makes our stomachs shout out?
Hunger is certainly a factor. When you haven’t chowed down in a two hours, receptors in the walls of your stomach trigger the hunger-arousing hormone ghrelin, which tattles to your brain that the pipe is empty. There are other things, like low blood sugar, that also send that message. And your brain, being the boss, steps in to solve that problem by releasing the hormone orexin, which tells your stomach it might be time to fill ‘er up again.

It’s the hypothalamus, which is in charge of body maintenance functions like controlling hunger, body temperature and your sex drive, that gets the credit for “switching on” that get me a hamburger feeling. It happens in stages.

First the hormone triggers your stomach’s smooth muscles to contract. Acids and other digestive fluids are deployed in the stomach and intestines to get the space ready for the next meal. The contractions move in a ring-shaped formation along your entire gut, forcing remaining mucus, food and bacteria from the area. These contractions produce vibrations, which are responsible for making the racket. The grumblings can last up to 20 minutes and repeat every hour or two until you’ve gotten food in your belly.

But the noises don’t only occur when you need food, although they’re louder in an empty cave; they happen after you’ve eaten, too. The contracting muscles of your stomach and small intestine are also responsible for mixing food with gas and fluid. These contractions move down the intestinal tract toward the exit just a few inches at a time. All this food/gas/liquid squishing also makes your stomach muscles vibrate, which produces a more tempered rattle.

Bad news is, there’s no way to tell it to simmer down. Hungry or not hungry, you’re going to have to put up with your stomach’s ruckus.

The real deal is strange and sometimes embarrassing, so we decided to get to the bottom of it. What is it that makes our stomachs shout out?
Hunger is certainly a factor. When you haven’t chowed down in a two hours, receptors in the walls of your stomach trigger the hunger-arousing hormone ghrelin, which tattles to your brain that the pipe is empty. There are other things, like low blood sugar, that also send that message. And your brain, being the boss, steps in to solve that problem by releasing the hormone orexin, which tells your stomach it might be time to fill ‘er up again.

It’s the hypothalamus, which is in charge of body maintenance functions like controlling hunger, body temperature and your sex drive, that gets the credit for “switching on” that get me a hamburger feeling. It happens in stages.

First the hormone triggers your stomach’s smooth muscles to contract. Acids and other digestive fluids are deployed in the stomach and intestines to get the space ready for the next meal. The contractions move in a ring-shaped formation along your entire gut, forcing remaining mucus, food and bacteria from the area. These contractions produce vibrations, which are responsible for making the racket. The grumblings can last up to 20 minutes and repeat every hour or two until you’ve gotten food in your belly.

But the noises don’t only occur when you need food, although they’re louder in an empty cave; they happen after you’ve eaten, too. The contracting muscles of your stomach and small intestine are also responsible for mixing food with gas and fluid. These contractions move down the intestinal tract toward the exit just a few inches at a time. All this food/gas/liquid squishing also makes your stomach muscles vibrate, which produces a more tempered rattle.

Bad news is, there’s no way to tell it to simmer down. Hungry or not hungry, you’re going to have to put up with your stomach’s ruckus.

Because of these online games’ immense popularity, Farmville and Starcraft gaming guides can be found all over the internet.  Strategies and tips to improve your game, as well as instructions for beginners, are available online.

Farmville is a very popular Facebook game application that is played within the browser.  The game basically allows you to vicariously live a life on the farm.  You can grow, harvest, and sell your own virtual crops.  Throughout the game, you earn game coins which you can use to upgrade your farm, buy new seeds, and set up your farm any way you see fit.

The game is very simple, but surprisingly – or perhaps because of its simplicity – it is actually fun to play.  With parental guidance, even a little child can learn to play the game easily.  It is ideal for the casual gamer to play once in a while just to break the monotony of any given day.

The game graphics are adequate and good enough, but the soundtrack can be boring after a while since the song is just played in the background over and over again.  However, there is an option to turn off the music.  There is also a photo option which allows you to take pictures of your farm that you can share with friends to update them on your progress.  Likewise, you can invite Facebook friends to be your neighbors or to help you out on some farm tasks.  You can also have friendly competition among yourselves to see who can sustain the best farm.

For more Farmville and Starcraft gaming guides, you can find tips and strategies for beginners, intermediate, and advanced players online.

Because of these online games’ immense popularity, Farmville and Starcraft gaming guides can be found all over the internet.  Strategies and tips to improve your game, as well as instructions for beginners, are available online.

Farmville is a very popular Facebook game application that is played within the browser.  The game basically allows you to vicariously live a life on the farm.  You can grow, harvest, and sell your own virtual crops.  Throughout the game, you earn game coins which you can use to upgrade your farm, buy new seeds, and set up your farm any way you see fit.

The game is very simple, but surprisingly – or perhaps because of its simplicity – it is actually fun to play.  With parental guidance, even a little child can learn to play the game easily.  It is ideal for the casual gamer to play once in a while just to break the monotony of any given day.

The game graphics are adequate and good enough, but the soundtrack can be boring after a while since the song is just played in the background over and over again.  However, there is an option to turn off the music.  There is also a photo option which allows you to take pictures of your farm that you can share with friends to update them on your progress.  Likewise, you can invite Facebook friends to be your neighbors or to help you out on some farm tasks.  You can also have friendly competition among yourselves to see who can sustain the best farm.

For more Farmville and Starcraft gaming guides, you can find tips and strategies for beginners, intermediate, and advanced players online.

Today Lets learn what is FishBone diagram and how to use it….

Description

Fishbone Diagram Procedure

Materials needed: flipchart or whiteboard, marking pens.

Agree on a problem statement (effect). Write it at the center right of the flipchart or whiteboard. Draw a box around it and draw a horizontal arrow running to it.

Brainstorm the major categories of causes of the problem. If this is difficult use generic headings:

Methods
Machines (equipment)
People (manpower)
Materials
Measurement
Environment

Write the categories of causes as branches from the main arrow.

Brainstorm all the possible causes of the problem. Ask: “Why does this happen?” As each idea is given, the facilitator writes it as a branch from the appropriate category. Causes can be written in several places if they relate to several categories.

Again ask “why does this happen?” about each cause. Write sub-causes branching off the causes. Continue to ask “Why?” and generate deeper levels of causes. Layers of branches indicate causal relationships.

When the group runs out of ideas, focus attention to places on the chart where ideas are few.

Let us know if you would like us to post this kind topics on Xcellextechnology Blog…we will continue doing on such topics…

Today Lets learn what is FishBone diagram and how to use it….

Description

Fishbone Diagram Procedure

Materials needed: flipchart or whiteboard, marking pens.

Agree on a problem statement (effect). Write it at the center right of the flipchart or whiteboard. Draw a box around it and draw a horizontal arrow running to it.

Brainstorm the major categories of causes of the problem. If this is difficult use generic headings:

Methods
Machines (equipment)
People (manpower)
Materials
Measurement
Environment

Write the categories of causes as branches from the main arrow.

Brainstorm all the possible causes of the problem. Ask: “Why does this happen?” As each idea is given, the facilitator writes it as a branch from the appropriate category. Causes can be written in several places if they relate to several categories.

Again ask “why does this happen?” about each cause. Write sub-causes branching off the causes. Continue to ask “Why?” and generate deeper levels of causes. Layers of branches indicate causal relationships.

When the group runs out of ideas, focus attention to places on the chart where ideas are few.

Let us know if you would like us to post this kind topics on Xcellextechnology Blog…we will continue doing on such topics…

All running applications that constitute development environments such as Web Matrix, Visual Studio.NET, etc., can all use the registered assemblies. The registering process of COM components in the server where ASP application are running is similar to adding an assembly to the Global Assembly Cache and the difference is that adding an assembly in Global Assembly Cache is much easier when compared to the act of registering COM components in a server with ASP applications.
In the first step you need to get the assemblies installed in the Global Assembly Cache for an effective sharing of assemblies. It is highly recommended to keep assembly dependencies separately and only in case of unavoidable necessity or an unambiguous need for sharing should you keep all the assemblies in the application directory itself. Further, there is no necessity for you to get all your assemblies installed in the Global Assembly Cache so as to make the assemblies accessible to COM interrupts or unmanaged code.

There are many ways with which you can install an assembly into the Global Assembly Cache and one such way is using an installer that is compatible with the Global Assembly Cache. Besides using the best method of using a Global Assembly Cache compatible installer for deploying assemblies, you can also make use of a tool that has been specifically developed for installing the assemblies into the Global Assembly Cache and the popular SDK is one such Global Assembly Cache tool developed for .NET Framework. Another easy method of installing assemblies into the Global Assembly Cache is through using the drag and drop option in Windows Explorer.

In any organisation, LAN administrators are vested with the responsibility of controlling access to various files and folders in WINNT directory by users and such LAN administrators accord read, write and execute permissions to users depending upon their hierarchy and roles in the organisation. LAN administrators make use of access control list that is available within the operating system and when the Global Assembly Cache is installed in the WINNT directory, the said Cache will inherit the access control list fully. You, as an administrator or a person responsible for the security of files, have to ensure that only people who have administrative privileges alone are able to access and delete files from the Global Assembly Cache.

You also need to ensure that you provide a strong name for the assemblies installed in the Global Assembly Cache, and note to perform all the integrity checks without fail on all files that constitute the installed assembly whenever you add or remove any assembly to or from the Global Assembly Cache. The main purpose of the carried out integrity check is to ensure that the files or the assemblies in the Global Assembly Cache are not tampered with, either intentionally or unintentionally.

The global assembly cache (GAC) is a machine-wide code cache that stores assemblies specifically designated to be shared by several applications on the computer. You should share assemblies by installing them into the global assembly cache only when you need to.
Steps:

- Create a strong name using sn.exe tool eg: sn -k mykey.snk
- in AssemblyInfo.cs, add the strong name eg: [assembly: AssemblyKeyFile("mykey.snk")]
- recompile project, and then install it to GAC in two ways :
• drag & drop it to assembly folder (C:\WINDOWS\assembly OR C:\WINNT\assembly) (shfusion.dll tool)
• gacutil -i abc.dll

The Global Assembly Cache or the popular acronym GAC refers to the machine-wide code cache in any of the computers that have been installed with common language runtime. The GAC or the Global Assembly Cache in .NET Framework acts as the central place for registering assemblies.

All running applications that constitute development environments such as Web Matrix, Visual Studio.NET, etc., can all use the registered assemblies. The registering process of COM components in the server where ASP application are running is similar to adding an assembly to the Global Assembly Cache and the difference is that adding an assembly in Global Assembly Cache is much easier when compared to the act of registering COM components in a server with ASP applications.
In the first step you need to get the assemblies installed in the Global Assembly Cache for an effective sharing of assemblies. It is highly recommended to keep assembly dependencies separately and only in case of unavoidable necessity or an unambiguous need for sharing should you keep all the assemblies in the application directory itself. Further, there is no necessity for you to get all your assemblies installed in the Global Assembly Cache so as to make the assemblies accessible to COM interrupts or unmanaged code.

There are many ways with which you can install an assembly into the Global Assembly Cache and one such way is using an installer that is compatible with the Global Assembly Cache. Besides using the best method of using a Global Assembly Cache compatible installer for deploying assemblies, you can also make use of a tool that has been specifically developed for installing the assemblies into the Global Assembly Cache and the popular SDK is one such Global Assembly Cache tool developed for .NET Framework. Another easy method of installing assemblies into the Global Assembly Cache is through using the drag and drop option in Windows Explorer.

In any organisation, LAN administrators are vested with the responsibility of controlling access to various files and folders in WINNT directory by users and such LAN administrators accord read, write and execute permissions to users depending upon their hierarchy and roles in the organisation. LAN administrators make use of access control list that is available within the operating system and when the Global Assembly Cache is installed in the WINNT directory, the said Cache will inherit the access control list fully. You, as an administrator or a person responsible for the security of files, have to ensure that only people who have administrative privileges alone are able to access and delete files from the Global Assembly Cache.

You also need to ensure that you provide a strong name for the assemblies installed in the Global Assembly Cache, and note to perform all the integrity checks without fail on all files that constitute the installed assembly whenever you add or remove any assembly to or from the Global Assembly Cache. The main purpose of the carried out integrity check is to ensure that the files or the assemblies in the Global Assembly Cache are not tampered with, either intentionally or unintentionally.

The global assembly cache (GAC) is a machine-wide code cache that stores assemblies specifically designated to be shared by several applications on the computer. You should share assemblies by installing them into the global assembly cache only when you need to.
Steps:

- Create a strong name using sn.exe tool eg: sn -k mykey.snk
- in AssemblyInfo.cs, add the strong name eg: [assembly: AssemblyKeyFile("mykey.snk")]
- recompile project, and then install it to GAC in two ways :
• drag & drop it to assembly folder (C:\WINDOWS\assembly OR C:\WINNT\assembly) (shfusion.dll tool)
• gacutil -i abc.dll

Explicit Memory Management
Let’s back up a minute and look at how unmanaged objects (written in C++, Delphi, etc.) are created and destroyed. Where is the data for an object and what is its lifetime? For a C++ programmer that is clear, he can decide the maximum speed by placing the object on the stack or in static storage. The stack is a fixed patch of memory area used by the microprocessor to store the data during the execution of the program. Using the stack places a priority on the speed of storage allocation and release, which can be very valuable in some situations. However, you sacrifice memory and flexibility because you must allocate the memory needed by the objects (even if you are not using them), know the exact quantity, lifetime and type of objects while you are writing the program. It’s enough to have the object declared in order to allocate the memory in the stack:

void main(void)
{
CFoo cfStack; // The costructor is called now. The destructor will be called when cfStack goes out of the scope.
}

Another approach is to create objects dynamically in the heap. With this latter approach you don’t know how many objects you need, what their lifetime is and what their type is until the program is running. If you need an object you have to make it on the heap with new keyword and then release it with delete keyword when that object is no longer used.

CFoo *cfHeap;
cfHeap = new CFoo(); // The constructor is invoked here.
cfHeap->PrintHello("Print hello from heap object.\n");
delete cfHeap; // The destructor is invoked here, the object is freed from the memory.

Creating the object in the heap is significantly longer than creating it on the stack because usually the latter operation is done by a single microprocessor instruction moving the stack pointer down and another to move it back up. But as said before, the advantage is measured in terms of memory usage where it is allocated only when required. Then, it’s possible to summarize the steps required to access an object as follows:

• Allocate memory heap for the type that represents the object with new keyword.
  Initialize the memory to set the initial state of the object and to make the object usable.
  Use the object (methods and fields).
  Clean up the state of the object.
  Free the memory from the heap with delete keyword.

This paradigm seems very simple but gives some problems to the developer:
The object is never freed (memory leak)
The object is freed when it needs to be used again (destabilization)
The object is freed more than once

These bugs cause an unpredictable behaviors in the application at an unpredictable times and then are very difficult to fix. There are many third-party tools (ie. TurboPower’s MemorySleuth, CompuWare’s BoundsChecker, Rational’s Purify, Task Manager, etc.) that help to detect these kinds of bugs.
As an alternative, the environment can provide a feature called a garbage collector that automatically discovers when an object is no longer in use and destroys it. Of course, a garbage collector is much more convenient, but it requires that all applications must run in all defined environment, such as the .NET Framework.

One of the new concepts introduced in the .NET Framework is the Garbage Collector (GC). In a very rough manner we can think about the GC as something that says, "never mind about your objects memory management, I will free it for you!" So, for the C++ programmer the question is, "do I need to use delete ?" The aim of this article is to explain how the Garbage Collector works under the .NET Framework.

Explicit Memory Management
Let’s back up a minute and look at how unmanaged objects (written in C++, Delphi, etc.) are created and destroyed. Where is the data for an object and what is its lifetime? For a C++ programmer that is clear, he can decide the maximum speed by placing the object on the stack or in static storage. The stack is a fixed patch of memory area used by the microprocessor to store the data during the execution of the program. Using the stack places a priority on the speed of storage allocation and release, which can be very valuable in some situations. However, you sacrifice memory and flexibility because you must allocate the memory needed by the objects (even if you are not using them), know the exact quantity, lifetime and type of objects while you are writing the program. It’s enough to have the object declared in order to allocate the memory in the stack:

void main(void)
{
CFoo cfStack; // The costructor is called now. The destructor will be called when cfStack goes out of the scope.
}

Another approach is to create objects dynamically in the heap. With this latter approach you don’t know how many objects you need, what their lifetime is and what their type is until the program is running. If you need an object you have to make it on the heap with new keyword and then release it with delete keyword when that object is no longer used.

CFoo *cfHeap;
cfHeap = new CFoo(); // The constructor is invoked here.
cfHeap->PrintHello("Print hello from heap object.\n");
delete cfHeap; // The destructor is invoked here, the object is freed from the memory.

Creating the object in the heap is significantly longer than creating it on the stack because usually the latter operation is done by a single microprocessor instruction moving the stack pointer down and another to move it back up. But as said before, the advantage is measured in terms of memory usage where it is allocated only when required. Then, it’s possible to summarize the steps required to access an object as follows:

• Allocate memory heap for the type that represents the object with new keyword.
  Initialize the memory to set the initial state of the object and to make the object usable.
  Use the object (methods and fields).
  Clean up the state of the object.
  Free the memory from the heap with delete keyword.

This paradigm seems very simple but gives some problems to the developer:
The object is never freed (memory leak)
The object is freed when it needs to be used again (destabilization)
The object is freed more than once

These bugs cause an unpredictable behaviors in the application at an unpredictable times and then are very difficult to fix. There are many third-party tools (ie. TurboPower’s MemorySleuth, CompuWare’s BoundsChecker, Rational’s Purify, Task Manager, etc.) that help to detect these kinds of bugs.
As an alternative, the environment can provide a feature called a garbage collector that automatically discovers when an object is no longer in use and destroys it. Of course, a garbage collector is much more convenient, but it requires that all applications must run in all defined environment, such as the .NET Framework.