Đang chuẩn bị liên kết để tải về tài liệu:
Professional ASP.NET 3.5 in C# and Visual Basic Part 111

Không đóng trình duyệt đến khi xuất hiện nút TẢI XUỐNG Tải xuống

Professional ASP.NET 3.5 in C# and Visual Basic Part 111. Building on the revolutionary ASP.NET 2.0 release, ASP.NET 3.5 adds several key new developer features including AJAX, LINQ, and a new CSS designer in Visual Web Developer 2008. The dramatic reduction in code that developers realized from the more than 50 new server controls in ASP.NET 2.0 now allows developers the time to make their applications more interactive with AJAX, to work with data in their preferred language with LINQ, and to build visually attractive and consistent standards-based sites with CSS. . | Chapter 22 State Management Figure 22-8 Additionally all URLS must be relative. Remember that the Session ID appears as if it were a directory. The Session is lost if an absolute URL such as myapp retrieve.aspx is invoked. If you are generating URLs on the server side use HttpResponse.ApplyAppPathModifier . It changes a URL when the Session ID is embedded as shown here Response.Write Response.ApplyAppPathModifier foo bar.aspx The previous line generates a URL similar to the following myapp S avkbnbml4n1n5mi5dmfqnu45 foo bar.aspx Notice that not only was session information added to the URL but it was also converted from a relative URL to an absolute URL including the application s virtual directory. This method can be useful when you need to use Response.Redirect or build a URL manually to redirect from an HTTP page to an HTTPS page while still maintaining cookieless session state. Choosing the Correct Way to Maintain State Now that you re familiar with the variety of options available for maintaining state in ASP.NET 2.0 here s some real-world advice from production systems. The In-Process InProc Session provider is the fastest method of course because everything held in memory is a live object reference. This provider is held in the HttpApplication s cache and as such it is susceptible to application recycles. If you use Windows 2000 Server or Windows XP the aspnet_wp.exe process manages the ASP.NET HTTP pipeline. If you re running Windows 2003 Server or Vista w3wp.exe is the default process that hosts the runtime. You must find a balance between the robustness of the out-of-process state service and the speed of the in-process provider. In our experience the out-of-process state service is usually about 15 percent slower than the in-process provider because of the serialization overhead and marshaling. SQL Session State is about 25 percent slower than InProc. Of course your mileage will likely vary. Don t let these numbers concern you too much. Be sure to do .