I understand that scope idea is based on statefullness of these mentioned frameworks. I can see the statefullness important (and useful) when you work on intranet applications that require a more complicated logic etc.
The viewScope starts on first page GET and lives for all POSTs to server and disappears on next GET to this page. If possible, it should be implemented with cache in web2py (IMHO) as it requires separate expiracy. With session and uniques keys for each page instance it would 'fill' session quickly. But I think its rather more general idea ... I mean if we can get some statefull nature in web2py it woul be great. . In JAVA world (where I come from) there are frameworks like Apache Wicket or Spring (marked as statefull) and those like Play! (marked as stateless). What is important that statefull frameworks can usualy run in stateless mode when required, but can operate with states when needed. -- --- You received this message because you are subscribed to the Google Groups "web2py-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
