in reply to Re^3: [RAKU] How to install zef on Ubuntu 22.04
in thread [RAKU] How to install zef on Ubuntu 22.04

"I have never needed them, nor wanted them (no need to post those massively annoying and now legally required cookie notices if not using them)."

Then don't use them?

"Now I am experiencing anomalies because of my hidden-field data"

Sounds like an issue with your code... which can happen regardless of the language used ;). Modern frameworks make life easier, and more fun, e.g. Mojolicious.

"updates are a massive headache when subroutines cannot accept named variables"

Perlcook book (2003?) - 10.7. Passing by Named Parameter.

"Raku's subroutines do support named variables, which would solve this problem and make my code more maintainable and future-proof."

Debatable.

  • Comment on Re^4: [RAKU] How to install zef on Ubuntu 22.04

Replies are listed 'Best First'.
Re^5: [RAKU] How to install zef on Ubuntu 22.04
by Polyglot (Chaplain) on Jan 10, 2024 at 13:51 UTC
    Then don't use them?

    I need to maintain a login session. Cookies appear to be the only viable solution when browsers now remember (cache) all the values of the form's hidden fields. I've been experiencing startling issues as a result, such as trying to login and the browser restoring the state of a different, previously logged-in, user, resulting in the wrong user logging in! In order to bypass this sort of behavior, I see no other way than to kow-tow to the cookie system that I have so long eschewed. Cookies aren't cached (as far as I know), and would be more secure, and more consistent, given that is what browsers have come to expect for session maintenance.

    Blessings,

    ~Polyglot~

[reply]
       I've been experiencing startling issues as a result, such as trying to login and the browser restoring the state of a different, previously logged-in, user, resulting in the wrong user logging in!

      you are obviously doing something seriously wrong. Even if 2 different users used the same computer, same browser to access your system one after the other, provided they pressed the logout button (and provided your logout procedure worked) there should be no trace of the previous user's data visible to the next. And if the previous user did not logout, then the next one should never arrive to the login screen anyway. Cookies can live on, they can be made to expire at some time, they can be made to expire immediately and erased from the browser, they can be kept alive on the browser but the session you keep can indicate "logout" state etc.

[reply]
[d/l]
        At one time I quite agreed with you. I thought I would be able to fix my "seriously wrong" code. It was only after much perplexity, failed attempts, and tons of internet-searching that I realized it was the browser's handling of the hidden form fields at issue. Trust me, I had cleared all of the session-related fields (via AJAX/JavaScript): this had no effect. Note that when I started out, this did work...but browsers have evolved. I was actually surprised to learn that the browser changes were not so recent as my noticing of the problem, and it turns out I may have been slower to catch on because I had been using an old computer with an old OS and older browser (barely functional with many websites these days). My "upgrade" just pulled the wool off my eyes. Perhaps I should feel a bit like Rip Van Winkle. In any case, I must now catch up to the times--though I still program on computers that are over 10 years old.

        Blessings,

        ~Polyglot~

[reply]

In Section Seekers of Perl Wisdom