Chapter 3 MTS, COM and VB - Intermediate Layer
3.1 Rule 3-1: Understanding MTS and COM Application Design
3.2 Rules 3-2: Do not use a single case in MTS or COM
3.3 Rules 3-3: Understand New, CreateObject and GetObjectContext.createInstance applications 3.3.1 MTS and Windows NT43.3.2 COM and Windows 20003.3.3 More problems with New New
3.4 Rules 3-4: Understand the true purpose of using SetComplete
3.5 Rules 3-5: Thinking on the method of automatic transaction
3.6 Rules 3-6: Don't redesign DBMS
3.7 Rules 3-7: Do not configure all components
3.8 Rules 3-8: Avoid compiling the things that will regret in the future into the DLL
3.9 Rules 3-9: Practice Tips from MTS from MTS to COM Transplantation 3.9.1 No longer need to call getObjectContext.createInstance3.9.2 as parameters in COM , no longer need to call Saferef3.9.3 when transaction Be careful when you want an object to return an error, you may get an error message such as "Method ~ of Object Failed ~", rather than the rich error message method returned by the error propagation, has been destroy. 3.9.4 Using ObjectConstruct strings 3.9.5 Perform declarative security checks when calling in a COM application 3.9.6 In Com , refreshing component commands is no longer required 3.9.7 in installation of Windows 2000. On the computer, COM export customer installer requires Microsoft Installer (MSI)
3.10 Rules 3-10: Writing Practical Skills Running Codes in MTS and COM 3.10.1 Creating an object When you adhere to getObjectContext.createInstance3.10.2 Use a programmable security to verify access, not to rely on a statement Sexual security measures 3.10.3 When the transaction method is called, it is best to use disableCommit in the secondary object instead of setabort3.10.4 Do not unintentionally install the DLL to the user's computer 3.10.5 insist on using ObjectContext interface 3.10.6 Distribution object reference Continue to use Saferef
Chapter 4 Web and VB
4.1 Rules 4-1: Understand the IIS Architecture
4.1.1 Internal Structure of IIS 4.1.2 Improves the expansion of servers
4.2 Rules 4-2: Manage the application status to achieve the highest efficiency 4.2.1 Using the BAS module data 4.2.2 Using SPM4.2.3 Using the ASP Application Object 4.2.4 Weighing the pros and cons of various programs
4.3 Rules 4-3: Managing session status to achieve maximum scalability 4.3.1 Limiting session on single machine 4.3.2 Store session information on the client 4.3.3 Using cookie4.3.4 querystring variable 4.3.5 hidden form field 4.3.6 Store status information in the database
4.4 Rules 4-4: Understanding DCOM and HTTP 4.4.1 Communication with RPC and DCOM 4.4.2 Using HTTP Communication 4.4.3 In distributed applications No ASP4.4.4 Using HTTP unfavorable aspects
4.5 Rules 4-5: Write COM Components (such as ASP) 4.5.1 Creating Default Interface 4.5.2 Passing Parameters To Writable Scripts 4.5.3 About Custom Interface 4.5.4 Solution
4.6 Rule 4-6: Understand how COM objects and ASP interacts 4.6.1 ASP built-in object 4.6.2 VB COM objects and STA4.6.3 Take advantage of the STA thread model 4.6.4 How to access the ASP built-in object in VB 4.6.5 Direct access to ASP built-in objects 4.6.6 Disadvantages with ASP built-in object 4.7 Rules 4-7: Use XML instead of proprietary data transfer format 4.8 Rules 4-8: Carefully consider the relationship between representations and business logic 4.8.1 Using MTS components 4.8.2 Using WebClasses
4.9 Rules 4-9: From the data to the XSLT implementation 4.9.1 XSLT concept 4.9.2 Benefits of the XSLT method 4.9.3 Using Process Method Translation Data Set 4.9.4 Using XSLT Method Translation Data Set 4.9.5 XSLT Disadvantage
