5 ms·
OK, I just realized that the example in the Arc-challenge might be possible to implement without the use of closures persisted between requests. If the page UR
by olavk 19y ago
OK, I just realized that the example in the Arc-challenge might be possible to implement without the use of closures persisted between requests.
If the page URLs are generated from the expression tree - outer expression is "/said", page 2 is "/said/anonymous1", page 3 is "/said/anonymous1/anonymous1" or something like that, the framework could locate and execute the correct expression for every hit.
The framework would have to be smart enough to detect that the "foo" input to the page 2 is used on page 3, so it is passed on in the generated link. This approach could actually be fully scalable.
(But damn! It would be disqualified because the input is passed from page 2 to 3 in the URL. I suppose it would be cheating to encrypt it?)
- aston 19y agoHint: many web stacks suppport server-side sessions. Via cookies.
- olavk 19y agoYeah, but you don't want to keep navigation state in the session. Otherwise you have to keep the session alive indefinitely to support bookmarking. Also, session based navigation state breaks if you browse the site in two tabs at the same time. And it breaks the back-button.
- aston 19y agopg's server-side closures are just a variation on the session theme, except that the data being stored is a procedure. You've just listed a bunch of flaws evident on this very forum . Any link with fnid as a parameter is pointing to a server-side session closure that might expire before you actually click the link.
- olavk 19y agoOK, agreed, I took your "hint" to indicate that you believed the problem could be solved by cookie-based sessions.