Monday 28 May 2007

Why shudnt i use Mobiles in Air planes???




Qn: I've noticed that I am not allowed to use my cell phone in airplanes or in hospitals. Why are these prohibitions in place?

Most of us experience electromagnetic interference on a fairly regular basis.

For example:
· If I put my cell phone down on my desk near the computer, I can hear loud static in my computer's speakers every time the phone and the tower handshake. In the same way, my car's tape player produces loud static whenever I make a call on my cell phone.
· When I dial a number on my home's wireless phone, I can hear the number being dialed through the baby monitor.
· It is not uncommon for a truck to go by and have its CB radio overwhelm the FM station I am listening to.
· Most of us have come across motors that cause radio or TV static.
None of these things, technically, should be happening. For example, a truck's CB radio is not transmitting on the FM radio bands, so my radio should never hear CB signals. However, all transmitters have some tendency to transmit at lower power on harmonic side bands, and this is how the FM radio picks up the CB. The same thing holds true for the wireless phone crossing over to the baby monitor. In the case of the cell phone affecting the computer's speakers, the wire to each speaker is acting like an antenna, and it picks up side bands in the audible range.
These are not dire problems -- they are just a nuisance. But notice how common they are. In an airplane, the same phenomena can cause big trouble.
An airplane contains a number of radios for a variety of tasks. There is a radio that the pilots use to talk to ground control and air traffic control (ATC). There is another radio that the plane uses to disclose its position to ATC computers. There are radar units used for guidance and weather detection, and so on. All of these radios are transmitting and receiving information at specific frequencies. If someone were to turn on a cell phone, the cell phone would transmit with a great deal of power (up to 3 watts). If it happens to create interference that overlaps with radio frequencies the plane is using, then messages between people or computers may be garbled. If one of the wires in the plane has damaged shielding, there is some possibility of the wire picking up the phone's signals just like my computer's speakers do. That could create faulty messages between pieces of equipment within the plane.

Many hospitals have installed wireless networks for equipment networking. The black antenna sticking out of the top of the monitor connects it back to the nursing station via a wireless network. If you use your cell phone and it creates interference, it can disrupt the transmissions between different pieces of equipment. That is true even if you simply have the cell phone turned on -- the cell phone and tower handshake with each other every couple of minutes, and your phone sends a burst of data during each handshake.

The prohibition on laptops and CD players during takeoff and landing is addressing the same issue, but the concerns here might fall into the category of "better safe than sorry." A poorly shielded laptop could transmit a fair amount of radio energy at its operating frequency, and this could, theoretically, create a problem.

Saturday 26 May 2007

HP has bagged $620M project!!

hi all,


Fortune has once again knocked IT major HP's door.

Hmm, they are going to provide Unix/Linux capabilities/desktop's/workstations servers and blade PC's to NASA's infrastructure for the worth $620m (£130m)!


Check this link,



Meet u all with another interesting topic soon!

Sunday 20 May 2007

Service Oriented Approach!


Dear all,

Let me give you a quick intro to the latest hot topic in the IT industry,hmm! yes, its the service oriented way of approach...,


SOA is a way of approaching the task of creating software. It can be thought of as either a collection of architectural concepts or a programming model. Within an SOA, all functionality is provided by services as described above. This provides a level of flexibility in deploying and reusing services not previously attained.

However, a SOA is more than just a collection of services; it adds a number of principles. Interoperability is the most important of these and is core to the idea of a SOA. Interoperability is achieved through the use of standards. The Web services standards stand out above all others in satisfying this requirement. Remote invocation is provided through SOAP, service interfaces are described using WSDL, and services are discovered through the use of UDDI. In fact, wherever possible, all aspects of the services should conform to the relevant standards. Showned are the sketch of SOA's approach & its benefits.
Another core feature of a SOA is the reuse of existing assets. Deployment of a SOA within an organization is an exercise in creating services from the existing IT systems and infrastructure. For example, systems exposed using object-based middleware are instead exposed using services that accept documents. Legacy systems such as mainframes can be exposed over standard transports and protocols.

Services should be self-contained, enabling them to be invoked directly by clients where necessary. SOA extends this idea to the aspects of services that might not be considered business logic. These include features such as security, logging, and auditing. Each service within the architecture should provide these features directly. This approach is vital if the deployed services are to form a truly distributed system. For example, a single point through which messages must flow in order to be audited leads to a hub-and-spoke architecture instead of the desired distributed system.
The use of a standardized protocol envelope is an important part of any SOA. The document payload for each service may differ, but a standardized protocol envelope provides a mechanism to support the processing of messages by intermediaries. Such mechanisms are used to support features such as addressing, routing, security, and policies. SOAP defines the envelope and numerous other standards define how headers within the envelope are used.
Once the SOA is in place, the existing IT systems within an organization can be viewed as services that provide business functions. These are easily integrated, because they provide well-defined interfaces and can be accessed using standard protocols and transports. This provides the basis on which to orchestrate services into new services that reflect business processes.

Presentation for the SOA could be found here,

Hope you enjoyed the concept of SOA!

Meet you all with another roborant topic! :)

Saturday 19 May 2007

Microsoft finally gets foot on online ad ladder!!

Microsoft today announced it will acquire aQuantive, the parent company of one of the industry’s most successful families of digital marketing in an all-cash transaction valued at $6bn (£3bn).
The huge sum paid by Microsoft - more than treble any of its previous acquisitions - shows its desperation to enter the online advertising market after it failed to acquire DoubleClick, Yahoo, or Real Media, all areas of interest.
Yesterday advertising group WPP said it will pay $637m (£322m) to purchase loss making web advertising broker 24/7 Real Media , and Google has also recently acquired DoubleClick for $3.1bn (£1.57bn).
Last week Microsoft was rumoured to be in takeover talks with Yahoo, but this latest deal will likely quell those rumours.
'The advertising industry is evolving and growing at an incredible pace, moving increasingly toward online and IP-served platforms, which dramatically increases the importance of software for this industry,' said Steve Ballmer, chief executive officer of Microsoft.
'Today’s announcement represents the next step in the evolution of our ad network from our initial investment in MSN, to the full capacity of the internet.'
The aQuantive acquisition enables Microsoft to strengthen relationships with advertisers, agencies and publishers by improving its advertising platforms and services beyond its current capabilities to serve MSN.
The acquisition also provides Microsoft increased depth in building and supporting next generation advertising solutions and environments such as cross media planning, video-on-demand and IPTV.

Friday 18 May 2007

Quote for the day!

"I shall inspire men everywhere until the world shall know that it is one with God"
--Swami Vivekanandha

Introduction to EAI!

Hi dudes,

Let me give you the definition of Enterprise Application Integration(EAI) today!

Enterprise Application Integration (EAI) is defined as the uses of software and computer systems architectural principles to integrate a set of enterprise computer applications.

In today’s competitive and dynamic business environment, applications such as Supply Chain Management, Customer Relationship Management, Business Intelligence and Integrated Collaboration environments have become imperative for organizations that need to maintain their competitive advantage. Enterprise Application Integration (EAI) is the process of linking these applications and others in order to realize financial and operational competitive advantages.
When different systems can’t share their data effectively, they create information bottlenecks that require human intervention in the form of decision making or data entry. With a properly deployed EAI architecture, organizations are able to focus most of their efforts on their value-creating core competencies instead of focusing on workflow management.
For generations, systems have been built that have served a single purpose for a single set of users without sufficient thought to integrating these systems into larger systems and multiple applications. EAI is the solution to the unanticipated outcome of generations of development undertaken without a central vision or strategy. The demand of the enterprise is to share data and processes without having to make sweeping changes to the applications or data structures. Only by creating a method of accomplishing this integration can EAI be both functional and cost-effective.
One of the challenges facing modern organizations is giving all their workers complete, transparent and real-time access to information. Many of the legacy applications still in use today were developed using arcane and proprietary technologies, thus creating information silos across departmental lines within organizations. These systems hampered seamless movement of information from one application to the other. EAI, as a discipline, aims to alleviate many of these problems, as well as create new paradigms for truly lean proactive organizations. EAI intends to transcend the simple goal of linking applications, and attempts to enable new and innovative ways of leveraging organizational knowledge to create further competitive advantages for the enterprise.



EAI is a response to decades of creating distributed monolithic, single purpose applications leveraging a hodgepodge of platforms and development approaches. EAI represents the solution to a problem that has existed since applications first moved from central processors. Put briefly, EAI is the “unrestricted sharing of data and business processes among any connected application or data sources in the enterprise.”
Undoubtedly, there are a number of instances of stovepipe systems in an enterprise, such as inventory control systems, sales automation systems, general ledger systems, and human resource systems. These systems typically were custom-built with specific needs in mind, utilizing the technology-of-the-day. Many used non-standard data storage and application development technology.