I previously discussed ways to manage user session state in DHTML-only UIs. A very similar problem arises with security contexts: Traditional web technologies like JSP and ASP.NET can link the identity of the user that is established at login to an authentication token that is either sent as cookie or encoded in the URL, just like the session id. If you integrate your session handling with a session-enabled technology as outlined in my earlier post, you can also attach to the security context in a similar fashion.
Continue Reading →
In my previous post I outlined a way of providing server-side user session state to a DHTML UI using native Java or .NET sessions. In this post I want to show another option: a web service-based solution.
As part of the WebDaptive AJAX framework, QAT offers a web service for both Java and .NET that mimics the main aspects of user sessions, including the generation of unique, hard-to-predict ids and customizable timeout of idle sessions. You can create and discard session objects, store, retrieve and delete key-value pairs via web service calls. The session id can be passed to other application components so they can access the session too.
Continue Reading →
In my previous post I mentioned that there is no built-in mechanism for associating calls from a pure DHTML UI with user and session-specific state at the server. In this post I want to detail how to integrate with a .NET or Java session. Of course, the same principles can be applied to other web technologies like PHP etc.
Continue Reading →
Often, web applications require storage of user-specific session state at the server. Depending on the application setup, the server will typically issue a session id which is mapped to the user-specific state data on the server. The session id is either transmitted as cookie or encoded in the URL and sent back to the server with each request the browser makes until the session is invalidated (explicitely by code or by timing out) or the browser is closed. Traditional Web applications with integrated AJAX features, utilize the session managament options of their underlying technologies; they work just as when using the base technology without AJAX enhancements.
Continue Reading →
This is the second installment of my AJAX overview. If you missed the first part, you can read it here. In this post I’d like to show two different approaches that AJAX frameworks usually take.
Server-side frameworks with AJAX integration Continue Reading →
Some AJAX frameworks combine dynamic page generation with AJAX components. This allows seamless integration of AJAX features with the advantages of the respective server-side technology. Much of the content is still dynamically created on the server like in a traditional UI but additional JavaScript code is added by the framework enabling AJAX-based features.
AJAX is one of the most commonly heard buzz words when it comes to Web user interfaces (Web UIs). I have now been working on several Web UIs using AJAX techniques and would like to share a few insights. I will start off with a review of how traditional web applications were – and still are – coded and how AJAX fits into this picture.
Continue Reading →
Connect with us: