.net pdf 417

.net pdf 417

.net pdf 417

.net pdf 417

.net pdf 417

.net pdf 417,
.net pdf 417,

.net pdf 417,
.net pdf 417,
.net pdf 417,
.net pdf 417,
.net pdf 417,
.net pdf 417,
.net pdf 417,
.net pdf 417,
.net pdf 417,
.net pdf 417,
.net pdf 417,
.net pdf 417,
.net pdf 417,
.net pdf 417,
.net pdf 417,
.net pdf 417,
.net pdf 417,
.net pdf 417,

.net pdf 417,
.net pdf 417,
.net pdf 417,
.net pdf 417,
.net pdf 417,
.net pdf 417,
.net pdf 417,
.net pdf 417,
.net pdf 417,
.net pdf 417,
.net pdf 417,
.net pdf 417,
.net pdf 417,
.net pdf 417,
.net pdf 417,
.net pdf 417,
.net pdf 417,
.net pdf 417,
.net pdf 417,
.net pdf 417,
.net pdf 417,
.net pdf 417,
.net pdf 417,
.net pdf 417,
.net pdf 417,
.net pdf 417,
.net pdf 417,
.net pdf 417,
.net pdf 417,
.net pdf 417,
.net pdf 417,
.net pdf 417,
.net pdf 417,
.net pdf 417,
.net pdf 417,
.net pdf 417,
.net pdf 417,
.net pdf 417,
.net pdf 417,
.net pdf 417,
.net pdf 417,
.net pdf 417,
.net pdf 417,
.net pdf 417,
.net pdf 417,
.net pdf 417,
.net pdf 417,
.net pdf 417,
.net pdf 417,

One vast improvement over raw C/API development is the use of the C++ programming language. In many ways, C++ can be thought of as an object-oriented layer on top of C. Thus, even though C++ programmers benefit from the famed pillars of OOP (encapsulation, inheritance, and polymorphism), they are still at the mercy of the painful aspects of the C language (e.g., manual memory management, ugly pointer arithmetic, and ugly syntactical constructs). Despite its complexity, many C++ frameworks exist today. For example, the Microsoft Foundation Classes (MFC) provides the developer with a set of C++ classes that facilitate the construction of Windows applications. The main role of MFC is to wrap a sane subset of the underlying Windows API behind a number of classes, magic macros, and numerous code-generation tools (aka wizards). Regardless of the helpful assistance offered by the MFC framework (as well as many other C++-based windowing toolkits), the fact of the matter is that C++ programming remains a difficult and error-prone experience, given its historical roots in C.

Due to a heartfelt desire to enjoy a simpler lifestyle, many programmers shifted away from the world of C(++)-based frameworks to kinder, gentler languages such as Visual Basic 6.0 (VB6). VB6 became popular due to its ability to build complex user interfaces, code libraries (e.g., COM servers), and database access logic with minimal fuss and bother. Much more than MFC, VB6 hid the complexities of the raw Windows API from view using a number of integrated code wizards, intrinsic VB data types, classes, and VB-specific functions. The major downfall of VB6 (which has been rectified given the advent of the .NET platform) is that it is not a fully object-oriented language; rather, it is object based. For example, VB6 does not allow the programmer to establish is-a relationships between classes (i.e., no classical inheritance) and has no intrinsic support for parameterized object construction. Moreover, VB6 doesn t provide the ability to build multithreaded applications unless you are willing to drop down to low-level API calls (which is complex at best and dangerous at worst).

Summary

Note The Visual Basic language used within the .NET platform (which is often referred to as VB.NET), has very

little relationship to VB6. For example, modern day VB supports operator overloading, classical inheritance, type constructors and generics.

After reading this chapter, you should be able to Code according to Drupal coding conventions. Document your code so that your comments can be reused by the API module. Comfortably search through Drupal s code base using grep. Identify Drupal coding ninjas by their best practices.

Although you have not overflowed the boundaries of an int data type, it should be clear that a mininovel with a page count of 30,000,000 pages is a bit unreasonable. As you can see, public fields do not provide a way to trap logical upper (or lower) limits. If your current system has a business rule that states a book must be between 1 and 1,000 pages, you are at a loss to enforce this programmatically. Because of this, public fields typically have no place in a production-level class definition.

Note To be more specific, members of a class that represent an object s state should not be marked as public. As you will see later in this chapter, public constants and public read-only fields are a-okay.

Drupal s core architecture is lean and written for flexibility. However, the flexibility comes at a price. As the number of modules increases, the complexity of serving a request increases. That means the server has to work harder, and strategies must be implemented to keep Drupal s legendary snappiness while a site increases in popularity. Properly configured, Drupal can easily survive a spike in visitors. In this chapter, we ll talk about both performance and scalability. Performance is how quickly your site responds to a request. Scalability has to do with how many simultaneous requests your system can handle and is usually measured in requests per second. This chapter is divided into two general sections, implementing tools and techniques that will help improve the performance of your site, followed by troubleshooting a slow-performing site. I ll start with the things that you should do before you get into a situation where your site is performing poorly.

Encapsulation provides a way to preserve the integrity of an object s state data. Rather than defining public fields (which can easily foster data corruption), you should get in the habit of defining private data, which is indirectly manipulated using one of two main techniques: Define a pair of accessor (get) and mutator (set) methods. Define a .NET property.