"Gertjan Klein" <[EMAIL PROTECTED]> wrote in message news:[EMAIL PROTECTED] > Peter Cooper wrote:
> >suppose you are in a shopping cart type app > >you need to navgate all over the place but still keep track of what > >was ordered - I believe that it is unrealistic to keep this in page > > Up to a point. Once an order has been entered, it should probably be > persisted (with a "pending" flag) until, say, payment details have > been entered. Done this way, it makes no difference if the user goes > back to the item selection page through the back button or an "add an > item" link you placed. This is a classic example of the mismatch between a normal application functionality and a technology that was never intended for running applications. >From the use of the back button the application never knows if the user wanted to go back to the state where an item wasn't ordered or just use it as a convenient way to return to the page that contained all the items to purchase. Rather sooner then later we have to leave this limited technology and use either Flash or SVG for pages that should look pretty and have all kinds of graphical design features and XForms for form based application type of pages. Note that both kind of pages can be data(base) driven and should be integrated with Cache is some way. > has high priority with ISC, though. It doesn't seem that CSP has any priority with ISC at all. I can't remember any significant additions or improvements to CSP the last years and I don't see any in 5.1 I can see CSP disappearing in a few years because of it's propriety nature but then ISC has to come with support for XForms in some form. Also integrating web applications with meta info from the database in the form of RDF functionality is something that should be supported by Cache' in the near future. Herman
