• Tim (unregistered)

    Huh? ArrayList is a list type not a map. You have to index it by number not by string

  • Hanzito (unregistered)

    Sweet! If you plan carefully, you can set the parameters for multiple calls efficiently, especially if you share parameter names that always have the same error. A revolution in decoupling and DRYness.

  • (nodebb)

    While I haven't seen this particular WTF, it's probably somebody who was trying to use MVC but got told they had to use shitty WebForms, and they didn't know about or didn't want to use MVP, so they tried to emulate MVC as best they knew how. A WTF to be sure but the idea seems at least based on "Structure the code so it's not a pile of garbage," even if they missed the point a bit.

  • AzureDiamond (unregistered)

    using a single session object instead of different singletons and global variables is not a bad practice... if its a real object not a dictionary

  • (nodebb)

    Are you sure this is the actual System.Collections.ArrayList? You can only index it by int, not by string

  • (nodebb)

    As mentioned before, it cannot be an ArrayList, it is more likely the old Hashtable which had System.Object as type for key/value and the indexer added new entries for non existing keys.

  • ThereAreMoreDepthsToPlumb (unregistered)

    I highly doubt that this ArrayList is System.Collections.ArrayList too, but there is absolutely no reason why this can't be class AcmeCorp.Collections.ArrayList extends System.Collections.Hashtable. Which makes this worse. But not as bad as the "but I liked the classic VB procedure dance" they've managed to re-create here.

  • (nodebb)

    Usually we pass functions arguments via the stack, but when you think of it the stack is just a global shared sort of hash map in a session after all...

    I'll see myself out now.

  • giammin (unregistered)

    a not so good news is that session will expire... you don't know when but be sure it will, without notice

  • Duke of New York (unregistered)

    Either Remy obfuscated the submission in a hurry, or some PHP coder had his way with ASP.

  • Jenda (unregistered) in reply to AzureDiamond

    Using a single session object sure as hell is an abysmal idea. Session is PER USER, not PER REQUEST! Imagine the user having two browser windows open at the same time, both showing a page of the same web, they submit a form in one and while the server's still cruching, they switch to the other window and click a link or a button. The second request will overwrite the first one's data in the session!

Leave a comment on “A Jammed Up Session”

Log In or post as a guest

Replying to comment #:

Log Out

« Return to Article