noloh Logo SmallDeveloper Zone
Username:
Password:
remember meforgot password?Login
twitterfacebookirc
plusfolder closePrinciples
plusdocumentWhat is NOLOH?
plusdocumentWhat's so Bad About Markup?
plusdocumentDevelopment and Philosophy
plusfolder closeFeatures
plusdocumentSyntactical Sugars
plusdocumentMultiple Inheritance
plusdocumentBookmarks and NOLOH
plusdocumentUser State Management
plusdocumentSearch Engine Friendly
plusfolder closeGetting Started
plusdocumentPHP and NOLOH Syntax
plusdocumentHello World
plusdocumentConstructors
plusdocumentInstalling NOLOH
plusfolder closeCrash Course
plusdocumentNOLOH and CSS
plusdocumentLayout in NOLOH
plusdocumentDatabases
plusdocumentData::$Links
plusdocumentEvents in NOLOH
plusdocumentMoving and Resizing Your Objects
plusdocumentMultiple Inheritance
plusdocumentBookmarks and NOLOH
plusdocumentData Binding
plusfolder closeAdvanced Topics
plusdocumentCustom Events
plusdocumentClientside Functions
plusfolder closeSyntactic Sugars
plusdocumentSyntactical Sugars
plusdocumentCascading
plusfolder closeCoding Guidelines
plusdocumentBest Practices
plusdocumentNOLOH Naming Conventions
User State Management
User State Managementoverviewdiscussion

Unlike the traditional webpage paradigm, one of the key advantages of NOLOH is the fact that it manages user state completely automatically and transparently. In other words, absolutely no work is required of the developer to manage user state. This creates a smooth and comfortable experience for both a user and a developer of a NOLOH-driven application. This mechanism works in two principal ways:

  1. A NOLOH application runs simultaneously on both the server and the client without either one terminating prematurely. Rather, when the server is not communicating to a particular client, it suspends information about the client's state only to be restored when it has need to. It will never forget the state and then have to recreate it completely from scratch, which is the common state of affairs of the "stateless" HTTP protocol..
  2. NOLOH also effectively and efficiently communicates changes in the state between the server and client. When the server determines that some object's visible properties must change, it notifies the client only of the necessary changes without redrawing unchanged material. Conversely, as a user uses his application, NOLOH will seamlessly keep track of important changes and communicate those changes to the server when necessary. Thus, through effective and organized communication, the distinction between server and client is profoundly blurred.

When taken together, these two mechanisms result in the automatic state management that is one of the key features of NOLOH's unique vision.

smallarrow
explanation arrowtool tip
handlebgexpand left
Right Up Outer CornerRight Down Outer CornerLeft Up Outer CornerLeft Down Outer Cornersearch-bottomclassconstantpropertymethodarticle
controltabsearchbig