in reply to Ways to maintain state in a CGI based card game

All the usual suspects - hidden fields, hidden frames, cookies, session ID and serverside files or even store the data in the query string of the form action (like link parsing on a tiny scale)....

In my opinion games are better handled in JavaScript or as a Java applet than using CGI because of the time delay and ugly refresh inherent in the CGI process.

cheers

tachyon

s&&rsenoyhcatreve&&&s&n.+t&"$'$`$\"$\&"&ee&&y&srve&&d&&print

  • Comment on Re: Ways to maintain state in a CGI based card game

Replies are listed 'Best First'.
Re: Re: Ways to maintain state in a CGI based card game
by vroom (His Eminence) on Aug 31, 2001 at 17:50 UTC
    Agreed. JavaScript or Java would be better suited for handling the game more quickly and in a more graphically pleasing fashion. I guess the stats I want to collect and my preference for Perl led me to a CGI solution. I could store information the game history in a JavaScript array or variable and then pass that along on game completion to a server side script for permanent storage and later analysis.

    vroom | Tim Vroom | vroom@blockstackers.com
[reply]

      Yes the question is often not "Could I do this in Perl?" but "Should I do this in Perl?" You can always do it in Perl! And you know once it is done you don't have hours of cross browser testing, tweaking, more testing, more tweaking, more testing..... to go :-)

      cheers

      tachyon

      s&&rsenoyhcatreve&&&s&n.+t&"$'$`$\"$\&"&ee&&y&srve&&d&&print

[reply]
        Amen Brother!

        -Lee

        "To be civilized is to deny one's nature."
[reply]

In Section Seekers of Perl Wisdom