Wimp Authentication

This script helps to protect against automated flood attacks, and requires the user to use cookies for user authentication.

1. Load wimpy.swf via HTML the way you normally would
2. Wimpy will make a request to your wimpyApp to load a playlist. Your wimpyApp should return the following string:

&auth=x&s=[session id]

Example:
&auth=x&s=12345

Where:

auth=x tells wimpy to check for authentication. "x" is a real value. i.e. only use "x" any other character will not work... just plain old "x"

s=[session id] is a unique identifier that wimpy will use for the entire session. Wimpy will both send and receive this unique ID when communicating with wimpyApp to receive a new playlist or server an mp3 file.

Do not send in any additional variables. Only send in "auth" and "s" as in the example provided earlier.

3. Once wimpy receives the "auth" and "s" variables, wimpy will make a second request to wimpyApp and include &auth=x&s=sessionId in the new request.

Example:
wimpy.swf issues:
yourapp.app?auth=x&s=sessionId

4. Your app should return auth=x&s=sessionID in subsequent responses to wimpy.swf in order for wimpy to continue working. If these parameters are no longer returned to wimpy, wimpy will display an error message.