Please discuss the necessity of high performance paging!
We can also see a lot of ways about high-performance paging, so-called, only the data on the Grid is displayed, and submitted each page, re-read the total M record starting from Nth item. To improve the performance of access. This method can reduce the transfer data between the client and the server, which can increase the page speed from a certain sense, but it is more troublesome: 1) Grid on the page does not directly use the binding function, you need to access the database first Read the count of the count (*) and calculate the GRID. 2) Unable to use the GRID's own paging function, whether it is MS or third part, require handwriting page code 3) When the "displaying each page of each page" is available on the interface, when the customer modifies this N value, the system It is necessary to reconstruct count. There is a special stored procedure on the Internet, used to return the records of nth to m, using two TOP methods, do not know such statements, how is the speed? And I have a view: adopting acknowledge, although the system will load data once, but the current hardware equipment is developing very quickly, can make up for a part, and on the interface, you can fully use the GRID function, development is quite Convenience. And the system does not do not return so-called tens of thousands of thousands, such a record number is paged, first is not realistic, it is estimated that few people will turn over a few thousand pages. Therefore, I feel that for the customer, the return of big data is not much, but it should be considered before n, even if it is big data, we don't have to return so much, as long as the first N If you are more, if you really want to display more, you can use a batch load function, such as loading n, the customer discovers is too small, and the N should be loaded. For the amount of data, the customer should be recommended to perform data queries to reduce the amount of data. So, in my thoughts, I have always think that there is no need to show the need for big data on the web, and I am very uncommon to display, and the page display is sometimes very inconvenient. For example, statistics for some data. The combined query is negative with the first N. If it is just a few hundred, I still advocate missed, let customers see all on the page, more convenient than one page. So I have been thinking, should I use high-performance paging? ? Is there such a necessary? I am worried that it is not so necessary for the pursuit. I hope everyone will discuss discussions. I am also melancholy. Supplement: The reason for thinking is to think: Do you want to add such a data segment back to the SPL? ? Is there any need?
2005-03-04 16:25 Author: Sonia listen .NET [Comments: 23] [read: 345]
Implement Types of Data Bindings (List) Controls
For a long time, please click here to read the full story
2005-01-18 15:55 Author: Capelin [Comments: 1] [Read: 741]
DNN (DotNetnuke) Research Handbook 5 DNN's future (blueprint)
The first chapter introduces the past, second, third, four chapters of DNN, briefly introduces DNN's this life, this chapter is a national day gift, bringing you the most exciting DNN future (blueprint), see DNN to become What kind of portal! DNN officially called blueprints with 3 phases: The first is Build (compilation), which is currently developing, basically function is completed, and some different improvements can be made. The second is Design (design), at this stage, all the ideas are completely discussed, conformally, each task has the person in charge, time consuming. The third is Concept (idea), in fact, in the community forum, the functional enhancement requirements proposed by the members, generally estimated that the Monkey is in the design phase, and may not be implemented later. At present, there are mainly: 1. Friendly Urls (friendly link), this is over the previous chapter, everyone will see; 2, localization (static) (localized - static), actually only puts the traditional HTML text is converted to ASP: Label; 3, Portal Search, the same 1 is currently in the Design phase, mainly: 1, Data MoDel (data model), improve the database design of DNN predecessor IBS; 2 , Document Security, role-based upload file management. Apply IIS file security .Resources extension protection mechanism, there is no need for additional databases or directory other than this application directory to reduce its restrictions; 3, File Manager, actually this has been advanced to 2.2x implementation, should Attributed to the build phase, it seems that the DNN's website update is too slow. This new file manager will implement multi-layer directories and role management of files with a tree list interface similar to the Windows Explorer: Only on the basis of simply uploading and deleting, the file will be copied, moved, Rename, you can save any layer directories. 4, Portal Module Definitions, until now, the association between the portal and modules is implemented through the PortalModuledEfinitions table, and the specific operation is to share with Host Fee to share in different sub-door. Now you have to transform, let Host Fee as an optional; 5, SSL (Secure Socket Layer), Yes, the portal implements SSL quite necessary; 6, WebLog Module, it seems that the blog is really hot, even Officials must be their own blog module.
Look at the time I have done Wiki (Wiki) :) 7, Windows Authentication, integrate Windows security mechanism, including domain, etc .; is currently in the Concept phase, mainly: 1, Authentication Identity certification), it seems that the network is too unsafe, and the safety law wants to achieve a safe portal; 2, Browser / Device Support (support for browser / device), (to be continued) 3, Core Modularization (core module Chemical, (to be continued) 4, localization (Content) (Localization - Content), (Renew) 5, Navigation Abstract (Browse Abstract), (Renewed) 6, Portal Groups, (to be continued) 7, SDK VERSION (Support for other non-VS.NET environments)? (Renew) 8, Web Farm Support (Enhance support for Web Farm)? (Continued) 9, WebPart Integration (Web component integration), (Continued) 2004-10-03 13:32 Author: Source of inspiration: PSP team Guru [Comments: 4] [Read: 785]
DNN (DotNetnuke) Research Technique Series 4-Frame (Hardcut) 1
Yes, this chapter I will introduce the hardenal injury of the DNN I understand. Everyone will read it, don't hurt, because I provide a solution in the process of actual development. :) I have been developing a system in the last for more than 2 months, which is a DNN as prototype. I spent nearly 2 months of research, summed up: there are several hard injuries in DNN. In fact, it is better to say that it is better to say that it is better to say that its current development space is better :) Although the reference selection is DNN, but we are just a reference, for the consideration of independent development and actual needs, we don't "copy" DNN Just learning its biggest feature: SKIN technology, and we feel that its Skin technology is quite mature, so we use our implementation method, but it is compatible with its SKIN / Container format, after all, is just XML / HTML explanation. DNN's largest hard injury: excessive looseness. This looseness does not mean that each module wants to build blocks, it can be placed in any column (tabs) and any position, but it means it. For example: publish an announcement. We generally have an announcement for a while, and this implementation in DNN can only: 1, modify the content of a bullet module instance; 2. Hide this module, create a module; 3, delete the module directly, Create a new module. Perhaps this example is not obvious, change one: article. The article should be the most common function, because most of the content can appear in the form of an article, including announcements, technical documents, news, FAQ, etc. How will we do it in DNN? It seems that only every article has created a new article module instance, if you don't want to display it (such as when you are)? It seems to be: 1, hide; 2, delete it directly. If you use methods 1, you are hidden, the page is very messy; if you use the method 2, if you want to find it? If there is a relaxing friend, it will propose the use of hidden columns to "reserve" these "orphans", but the quantity will still be messy! Also, if you want to retrieve and operate all the same type of module, what should I do? I believe you will switch back and forth between all columns. Similarly, other modules are the same. DNN built-in modules are just demonstrating their functions, as it's a framework, not making functional content. In fact, can you think of how to solve it? What I can think of is to do a centralized list management. The advantage of list management is that at any time, you can do any articles, don't have to change back and forth between the columns. that's it? No, let's go further: Be a general document management system! In fact, whether it is an announcement, technical documentation, news, FAQ, etc., generally includes: authors, sources, creating months, text content, introduction, page open type (such as this page, new page, etc.), status (if not Approval, approval, hidden, etc.), icon, etc. that's it? No, let's go deep into the point: add type management! Types can be widely used in any layer column, articles type, and so on. In this way, you can choose the category to choose the category when editing. that's it? No, let's have a thorough revolution: set types and general articles to integrate multiple universal modules. Such as: 1, a class list: You just need to list all level types, so that users define which type and how many of the categories, sort by date.
In this way, once a type is selected, the Top N article to which this type belongs is listed. Is it flexible? 2, the hottest article recommendation: This is simpler, select a type, then select an article under certain types to define a personalized picture, just like this. Then get an icon on the left when the specific display is displayed, and the bold title and introduction are displayed on the right. Is it flexible? 3, theme news: This is the easiest, followed 2 is almost the same, the only difference is to display the content directly, the effect is similar to the largest Flash / Image effect similar to the Microsoft home page, click to enter the specific column or article. Not flexible enough? Ok, look down: (Everyone pays attention to the benefits? No matter how many modules, only need to define an article, any article can now re-definition, do not have to worry about a module delete the article lost in view of the great room for development DNN can now introduce only the first, then there will be even more interesting:) 2004-09-23 21:42 author: source of inspiration: PSP team Guru [comment : 10] [Read: 871]
DNN (DOTNETNUKE) Research Handbook 3-Framework (Overview)
From this chapter, the DNN's framework, DNN's framework can be divided from the following angles: 1, directory, China Rainbow has written more details on the use of each directory and various documents, I am no longer repeated, I only from the main frame Say: a. Management: a1. Container A2. File (File) A3. Module Definition (PAUPLOAD) A5. Portal (Portal) A5. Apperta A6. Appearance / Skin ( Skin) A7. Column / Label (Tabs) A8. User (User) B. Components B1. Logging) B2. Logging B3. Scheduling C.UI Control: c1.html Editor Device (DesktopModules) can be seen from the desktop module (DesktopModules), and the DNN's directory framework is quite compact. You can only see several files in the root directory, and the management directory is the core, function of the entire portal. Components are skeletons, UI controls are core applications, and desktop modules are specific business applications. 2, according to the core function, DNN can be divided into the following: A, Appearance / Skin, including Skins, Tabs, Modules, Moduledefinitions, Containers, etc. , Security, Files, etc .; It is seen that Skin's status is the most intimate in DNN. DNN has a lot of .NET technology, such as a large number of inheritance, heavy duty, proxy, etc., implements an abstract data access (Datacche), multithreaded schedule (SCHEDULING), error handling (Exceptions) , Empty type (NULL) and other functions, I will introduce the characteristics, implementation and application of various technologies one by one.
2004-09-04 13:32 Author: Source of inspiration: PSP team Guru [Comments: 18] [read: 1659]
DNN (DotNetnuke) Research Handbook Series 2- Background, Status Quo
First of all, please don't be busy looking at this article, try to download a new version to install the latest version, take a closer look at the installation instruction document, the white paper of various technologies, DNN is very very careful, even version code difference Both fine to each line code. Why not take care of it? Is DNN? DNN can be traced back to ASP.NET Portal of ASP.NET Starter Kits, which can still be found in the ASP.NET website. Related articles I have written before, please search it yourself. After ASP.NET Portal, IBuyspy appeared, which is a familiar IBS, which has evolved a lot than ASP.NET Portal, using a lot of .NET technology, the prototype of DNN. In 2002, IBS confirms its limitations to the market that cannot meet user needs, DNN1.x is launched, and it mainly improves module function on the basis of IBS, and the next DNN2.0.x is more written throughout the core. Brought revolutionary SKIN. Does DNN have a popularity? 1, dotNetnuke: http://www.dotNuke.com/ Official site daily registration / access, you can look at the online statistics on the right of your home; 2, DNN Forum http://www.asp.net/forums/ Showforum.aspx? TabINDEX = 1 & forumID = 90 is a relatively hot, relatively hot on the ASP.NET website; 3. DNN is wide in numerous free / charge portal; 4, DNN2.0.X release In Microsoft VS-LIVE! Conference, it is demonstrated, huh, huh; in the study, I feel that I am not waiting for others to feed myself, but I don't like it to eat, maybe this is not an appropriate, meaning, I mean, To study, you will take yourself more than waiting for others. DNN advocates an preparing, dynamic, 100% interactive data-driven network portal framework. The maximum DNN is characterized by the system frame, DSL (data storage layer), DAL (data access layer), BLL (service logic layer), and PL (rendering layers) are completely separated. System developers, business developers, artists, and DBA (database administrators) are "mutually disconnected". In order to be as compatible with .NET 2005, DNN applies a lot of so-called Provider (provider) / factory model to achieve its extensive scalability, maybe you will feel that only one data is updated, you want to be in 3 The class is implemented, but when you want to switch between MS SQL, Access, MySQL, Oracle or XML, then you will find that DNN mode will make you pleasant. Another feature of DNN is its SKIN (Appearance) that implements the dynamic appearance from Portal (portal), Tab (column) to Module (module), each Skin division SKIN and Container, Container can understand Each module is included in a Container into a module area of DNN. DNN's SKIN and dynamic module are inseparable. DNN's Tab and Module definitions have arrived at Wysiwyg, but I don't think of concentration. Every module of DNN can be understood as a building block, you can put this building block in any position of any column, you can even hide it. However, DNN does not have a concentration for each module's data processing, and Module deletes, does not generate a large amount of redundant data from the time of automatically deleting the corresponding data.
And there is no centralized treatment, it is very unintervision. I have improved in practical applications. If you just think that DNN's SKIN is just changing CSS and changed a picture, if you think .Text can be compared with DNN, then you are wrong. With the kernel of DNN, you will definitely change. DNN will then launch 2.2x in October, improvements include: 1, portal search; 2, friendly URL, path no longer display /Default.aspx?tabid=xx, but may be / portal / 0 / tab / 11 / Page /; 3, multi-language; in Zhang 3, I will understand DNN, press the function to introduce the framework. 2004-09-01 20:17 Author: Source of inspiration: PSP team Guru [Comments: 24] [read: 1280]
DNN (DOTNETNUKE) Research Handbook 1- Resources
