I have been leading the research on ITOO's CAS for a while, and it seems that it has been quit, but it has always been pathological. As the saying goes, if you are sick, you have to cure it. If you can't cure it, you have to find a way to cure it. The same path continues. We are in a cycle of finding out where we went wrong and why we couldn’t achieve it. In fact, we can break out of this vicious circle and use another method to solve this problem.
Since the current CAS cannot be used and SSO exit cannot be implemented, then we will write our own CAS using the logic of single sign-on. During the writing process, Daqu was the leader and I was the manager. Later, I was given a small task, which was to change the server control into an HTML client control. I didn’t know why at that time, but now let’s study the difference between these two controls.
This goes back to the Asp.net control.
, not controlled by the server, and can only be controlled on the client through programming languages such as js and other language scripts. For example,
2. HTML server control:
In fact, it is composed of html control plus runat="server" Controls. Their running methods are different. The html control runs on the client side, while the html server control runs on the server side. When the ASP.NET web page is executed, it will check whether the annotation has the runat attribute. If the annotation is not set, then the Html The annotation will be treated as a string and sent to the string stream to wait for delivery to the client. The client's browser will interpret it; if the Html annotation has the runat="server" attribute set, the Page object will When the control is placed in the controller, the server-side code can control it. After the control is executed, the execution result of the Html server control is converted into Html annotations, and then sent to the client as a string stream for interpretation.
<inputtype="button" id="btn" value="button"/>
3. Web server control: also called Asp.net server control
It is the basic element of WebForm programming and also asp.net server control. net-specific. It will generate one or more html controls according to the client's situation, rather than directly describing html elements. Such as:
<inputid="Button" type="button" value="button"runat="server" />
Then
What is the difference between Asp.net server control and html server control?
1. Asp.net server control provides a more unified programming interface, such as each Asp.net server Controls all have a Text property.
2. Asp.net server control hides the differences between clients, so that programmers can focus more on business without having to consider whether the client's browser is IE, Firefox, or a mobile device.
3. Asp.net server control can save state to ViewState, so that the page can be saved during the process of being sent back from the client to the server or downloaded from the server to the client. 4. The event processing model is different. The event processing of Html annotation and Html server control is on the client page, while the Asp.net server control is on the server.
Summary:
The events of Html annotation and Html server control are triggered by the page, while the Asp.net server control is triggered by The page sends the Form back to the server for processing by the server. This was my question at the beginning. The server control will refresh the entire page after being clicked, but the client control will not. The effect we want is that starting a control will not refresh the entire form.
I seem to be a little unfamiliar with Asp.net. When I use the things I have learned, I still need to check them online and cannot just pick them up. Still, the knowledge we have learned has not been put together to form a net. So, study, young man, one day you will be happy for your efforts...
Copyright statement: This article is an original article by the blogger and has not been published by the blogger. No reproduction allowed with permission of the owner.