Server-side? Client-side? Who cares?



  • I'm sure there's a reasonable explanation for this, but, when I first saw it, I thought "WTF?"

    All I need to show is the left-hand side of the assignment; what's on the right doesn't matter.  C# on ASP.NET, FWIW.

    Session["Cookie"] = ... 


  • This sounds to me like some sort of reflection-like "cleverness":

     

    Client-side:

    // Use a unique name for the cookie so teh user does'nt red it

    var name = genreateUniqueCookieName();

    SetCookie(name, bigScret);

     window.location = window.location + '?secritCooikieNam=' + name;   // Sendto server



  • @JeffS said:

    I'm sure there's a reasonable explanation for this, but, when I first saw it, I thought "WTF?"

    All I need to show is the left-hand side of the assignment; what's on the right doesn't matter.  C# on ASP.NET, FWIW.

    Session["Cookie"] = ... 

     

    Maybe whoever wrote that heard about session cookies and immediately thought, "I've got to get me some of that! - I'll just store the name of the session cookie in the session. Brillant!"



  • Does this application run in a cluster?

     Regardless, people who don't address session by using HttpContext.Current usually suck at coding anyways.



  • WTF?  We just lost Davek's and my post.

    Davek, did you delete your own post?

    PS.  I got a "forum not found" error when trying to post a reponse to your post.  @Community Server said:

    WTF is a decent error message?


Log in to reply
 

Looks like your connection to What the Daily WTF? was lost, please wait while we try to reconnect.