Persistent Janus Web Applications
SUG '04
Presentations
Click on any slide to view a linked version of this presentation.

Slide 1: Alex Kodat

Slide 2: Agenda

Slide 3: So What is a "Persistent" Web Application?

Slide 4: How Persistent is Persistent?

Slide 5: Some Reasons for Persistent Applications

Slide 6: The Attainable Ideal - All State Data Held by Client

Slide 7: Conversational Web Application

Slide 8: Janus Web Legacy Applications

Slide 9: Making Janus Web Legacy Screens Look Prettier

Slide 10: $Web_Form_Done

Slide 11: How Does $Web_Form_Done Work

Slide 12: Janus Web Processing for Request in $Web_Form_Done

Slide 13: Problem - Suppose User Manages to Double-Post a Page

Slide 14: Check Parameter Example

Slide 15: Let's See $Web_Form_Done In Action

Slide 16: $Web_Form_Done

Slide 17: One Other Gotcha with $Web_Form_Done

Slide 18: More Advanced Persistence Techniques

Slide 19: Brute Force

Slide 20: Benefits of Brute Force

Slide 21: Problems With Brute Force

Slide 22: $Web_Save_Recset and $Web_Save_List

Slide 23: An Alternative - $Session Functions

Slide 24: $Session Functions

Slide 25: Using Sessions

Slide 26: Let's See Sessions In Action

Slide 27: Coming Soon - Session Objects

Slide 28: Session Object Problems

Slide 29: Conclusion

Slide 30: Coming soon!


Sirius location

The Sirius site runs as a Model 204 application using the Janus Web Server.
This page and all contents are Copyright © 2004 by Sirius Software, Inc., Cambridge, MA.