Cyclomatic complexity measures the amount of decision logic in a single software module. It is used for two related purposes in the structured testing methodology.First, it gives the number of recommended tests for software. Second, it is used during all phases of the software lifecycle, beginning with design, to keep software reliable, testable, and manageable. Cyclomatic complexity is based entirely on the structure of software's control flow graph.

A set of computers that work together to provide a service. The use of a cluster enhances both the availability and scalability of the service. Network Load Balancing provides a software solution for clustering multiple computers running networked client/server applications.

Comega :Microsoft bridging relational, object, XML data models.

Comega is programming technology, which is intended to bridge the gap between relational, object, and XML data models.

Comega, is described by Microsoft as a strongly typed, data-oriented programming language to bridge semi-structured hierarchical data (XML), relational data (SQL) and the .Net CTS (Common Type System). Additionally, Comega extends C# with asynchronous concurrency abstractions.

Comega tackles the issue of having to write repetitive code based on Microsoft’s ADO (ActiveX Data Objects) .Net technology

ADO.Net is great but it's a lot of repetitive code that you have to write again and again, and Comega provides a direct way to put SQL queries in your code base without the repetitive code

The imperative language model requires the user to determine what the end result should be and also tell the computer step by step how to achieve that result.
It is analogous to asking a cab driver to drive you to the airport and then giving him turn by turn directions to get there.
SQL is different from many common programming languages such as c++ and visual basic because it is a declarative language. Languages such as c++, visual basic, c# and even assembler are imperative languages.

Declarative languages such as SQL, on the other hand let you frame problems in terms of the end result. All you have to do is describe what you want from SQL
Server via a query and trust the database engine to deliver the correct result as efficiently as possible. To continue the cab driver analogy from earlier, in a declarative language you would tell the cab driver to take you to the airport and then trust that he knows the best route.

Scaling Up Versus Scaling Out Database Server?

Scaling Up Vs. Scaling Out. When web application traffic grows there are two ways to handle it. Either Scaling Up or Scale out, what is it specially in case of Database server?

The most common approach to scaling applications is to scale them up. In essence, scaling-up simply means to keep increasing the resources (hardware) available on the server, allowing it to handle more load and user requests. The reason that this approach is so common is because it requires no change to the actual application and all of the data is in one place, which certainly helps reduce complexity and maintenance.

The second and more complex approach is scaling-out. The basic idea is to partition data across several database servers and therefore splitting the load of the application across multiple servers.

While scaling out web servers can be done quite easily, properly scaling out database servers is far more challenging.

What is strong-typing versus weak-typing? Which is preferred? Why?

Strong type is checking the types of variables as soon as possible, usually at compile time. While weak typing is delaying checking the types of the system as late as possible, usually to run-time. Which is preferred depends on what you want. For scripts & quick stuff you’ll usually want weak typing, because you want to write as much less code as possible. In big programs, strong typing can reduce errors at compile time.

Weak typing is where a language allows you to treat blocks of memory defined as one type as another (casting). Languages like C and C++, although statically typed, are weakly typed.

Languages like Perl and PHP are weakly typed because you can do things like adding numbers to strings and the language will do an implicit coercion for you.
Languages like Java, C# and Python are strongly typed - there is no way you can add a number to a string without doing an explicit conversion.

3G is a short term for third-generation wireless, and refers to near-future developments in personal and business wireless technology, especially mobile communications.

3G is include features such as:
·Enhanced multimedia (voice, data, video, and remote control)
·Usability on all popular modes (cellular telephone, e-mail, paging, fax, videoconferencing, and Web browsing)
·Broad bandwidth and high speed (upwards of 2 Mbps)
·Routing flexibility (repeater, satellite, LAN)
·Operation at approximately 2 GHz transmit and receive frequencies

3.5G is better than the much touted `3G' or third generation mobile networks where high speed data, voice and video can be exchanged.
The zippy new technology, is known as HSDPA — High Speed Data Downlink Packet Access — industry jargon which means the download speeds at which video or data can be sucked into a mobile phone could theoretically be as high as 10 mega bits per second (MBPS) — but in practice would be around a half to one-third this speed. It is the next evolutionary step in speeding up today's GSM or Global Services Mobile networks after it has upgraded to EDGE — Enhanced Data Rate for GSM and WCDMA — Wide Band Code Division Multiple Access.

some of famous 3.5g mobiles are nokia n95,nokia 6110 classic

What does the acronym UMTS stand for?
Universal Mobile Telephone System.

What is UMTS?
UMTS is one of the Third Generation (3G) mobile systems being developed within the ITU's IMT-2000 framework.

Before the .NET Framework existed, Windows had two levels of trust for downloaded code. This old model was a binary trust model. You only had two choices: Full Trust, and No Trust. The code could either do anything you could do, or it wouldn’t run at all.

The permission sets in .NET include FullTrust, SkipVerification, Execution, Nothing, LocalIntranet, Internet and Everything. Full Trust Grants unrestricted permissions to system resources. Fully trusted code run by a normal, nonprivileged user cannot do administrative tasks, but can access any resources the user can access, and do anything the user can do. From a security standpoint, you can think of fully trusted code as being similar to native, unmanaged code, like a traditional ActiveX control.

GAC assemblies are granted FullTrust. In v1.0 and 1.1, the fact that assemblies in the GAC seem to always get a FullTrust grant is actually a side effect of the fact that the GAC lives on the local machine. If anyone were to lock down the security policy by changing the grant set of the local machine to something less than FullTrust, and if your assembly did not get extra permission from some other code group, it would no longer have FullTrust even though it lives in the GAC.