![]() If the user does not access a page of the application within this time-out period, ColdFusion interprets this as the end of the session and clears any variables associated with that session. Therefore, sessions always terminate after a time-out period of inactivity. In most cases, however, a web application has no way of knowing if a user has finished or is just lingering over a page. A session should end when the user finishes using an application. However, because of the stateless nature of the web, it is not always possible to define a precise point at which a session ends. This logical view of a session begins with the first connection to an application by a client and ends after that client's last connection. ![]() As a result, every user of an application has a separate session and has access to a separate set of session variables. Sessions are specific to both the individual user and the application. What is a session?Ī session refers to all the connections that a single client might make to a server in the course of viewing any pages associated with a given application. For information on using cflock tags see "Locking code with cflock". ![]() (Use client variables if you need a variable in multiple visits.)Ĭaution: To preserve data integrity, put code that uses session variables inside cflock tags. For example, you might use session variables to store a user's selections in a shopping cart application. Use session variables when you need the variables for a single site visit or set of requests. Developing ColdFusion MX Applications with CFML
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |