To install via MakeMaker, it's the usual procedure - download from CPAN, extract, type "perl Makefile.PL", "nmake" then "nmake install". Don't do an "nmake test" because the ASP objects won't be available and so won't work properly.

This imports the following methods into the Win32::ASP namespace. There is no need to use Win32::ASP; in order to use Win32::ASP::Extras;. The modules are independent of each other and only share a namespace.

To be more precise, use Win32::ASP::Extras' loads everything into Win32::ASP::Extras and then aliases the symbol table entries over into Win32::ASP. This is to avoid any weirdness with respect to AutoLoader.

This is designed to take a base URL and a hash of parameters and return the properly assembled URL. It does, however, have some weird behavior.

If the first character of the URL is not a forward slash and $main::WEBROOT is defined, the function will automatically prepend $main::WEBROOT/ to the URL. This has the side effect of making 95% of URLs absolute relative to $main::WEBROOT, if it is defined. This makes it easier to move Webs around just by changing $main::WEBROOT.

If the first character of the URL is a forward slash, the URL is left unchanged.

If the first characters are "./", the "./" is stripped off and the URL left unchanged. This allows one to specify relative URLs - just put a "./" in front of it.

The parameters are URLEncoded, but the keys for them are not. The resultant parameter list is HTML encoded so that &timestamp doesn't become xtamp (&times; encodes a multiplication symbol).

A safe redirect that redirects and then absolutely and positively terminates your program. If you thought $Response-Redirect> behaved liked die and were disappointed to discover it didn't, mourn no longer.

It takes a base URL and a hash of parameters. The URL will be built using FormatURL.

The function returns both passurl and the result from calling MyURL. The return values are suitable for inclusion in a hash for passing to FormatURL. The PassURL functions are generally used for dealing with expired sessions. If the session expires, the Redirect is passed CreatePassURLPair for the parameters. That page then explains to the user what is going on and has a link back to the login page along with PassURLPair. The login page can then use GetPassURL to extract the URL from the QueryString and redirect to that URL.

Set and Get can be used to store arbitrary Perl objects in $Session. It uses Data::Dumper to store things and eval to retrieve them. Notice that this is safe only because we are the only ones who can store stuff in $Session.

<LECTURE_MODE>

Do NOT, I repeat, do NOT use Data::Dumper to serialize a Perl object and then stuff it in a user's cookie, presuming that you can then use eval to extract it when they pass it back to you. If you do, you deserve to have someone stuff system("del /s *.*") or some such funny Perl code in that cookie and then visit your web site. Never, ever, ever use eval on code that comes from an untrusted source. If you need to do so for some strange reason, take a look at the Safe module, but be careful.

</LECTURE_MODE>

Oh, the call takes two parameters, the name to store it under and the thing to store (can be a reference to a hash or some other neat goodie). Keep in mind that references to CODE objects (i.e. anonymous subroutines) or Win32::OLE objects or anything like that will not make it.

Takes a parameter and returns the thing. Both Set and Get use the same memoization cache to improve performance. Take care if you modify the thing you get back from Get - future calls to Get will return the modified thing (even though it hasn't been changed in $Session). Calls to Set empty the memoization cache so that the next call to Get will reload it from $Session and add it to the cache.