Blogs : Archives
|
|
| < The monolithic Laszlo application | Laszlo 3.0b2 released, a step in the right direction > |
|
I'm posting this as a reply to the following blog post and more particularly the following line. "Your server-side session has expired, and your work is gone." The RIFE framework has solved this many years ago. We have something similar as actions, but we call them elements. Elements are components that talk together through a site structure. That site structure is not limited to be two-dimensional, you can layer many site structures on top of each-other with child triggers that make the engine jump to the underlying layer. If a request arrives that is intended for a lower layer, and the conditions for the upper layer's child triggers aren't present, the initial request state is serialized and preserved. You can perform a flow of any kind of complexity in the upper layer, the serialized state will be automatically passed around. As soon as the trigger to go to the underlying layer occurs, the original request state is de-serialized and the element for who the original request was intended receives the data you sent initially. We call this behavioural inheritance and implemented authentication with it. So when your user session times out, you don't go beyond the authentication site structure where you can identify yourself. As soon as you have successfully identified, a child event is triggered and you go to the lower layer that receives the data you posted when the session timed out. If you want to try this out do the following:
This is one of many areas where a powerful framework can help you. Many frameworks merely structure well know approaches and practices in a personal fashion. They don't offer many new solutions to complex problems. Be sure to evaluate which framework you choose for a project thoroughly, there might be lesser known alternatives that maybe offer ready-made solutions to many of the problems that you will be facing. |
Comments |
Add a new comment |
| Comments on this blog entry have been closed. |
| < The monolithic Laszlo application | Laszlo 3.0b2 released, a step in the right direction > |


