Re: CGI.pm parsing odity
- From: xhoster@xxxxxxxxx
- Date: 16 May 2006 16:50:13 GMT
you.did@xxxxxxxxxxx wrote:
Hello.
With CGI.pm Oo_style coding,
I use a form with GET method, it parses a textfield with name
attribute:
"participant".
I validate that parameter with Perl's substitute and match handlers in
order to make a file in "/tmp/SOMEDIR/" with names like :
"participant.scorefile".
In that file i regulary use the CGI function save() to save the satus
of
the form and it writes away an annoying trainling "=".
If that is the biggest annoyance you face, you are a lucky man indeed.
$]cat /tmp/SCORES/JohnDoe.sorefile
gives this :
participant=JohnDoe
=
Have you bothered to read the documentation for the method you are using?
from perldoc CGI on save():
Both name and value are URL escaped. Multi-valued CGI
parameters are represented as repeated names. A session
record is delimited by a single = symbol. You can write
out multiple records and read them back in with several
calls to new.
That is "$query save(FHANDLE);" right after the participant puts his
name, so, the *wanted* dated is in there but I don't know where Perl
gets that empty form parameter, is it even empty form data ? Is it an
assignment ? Why this trailing "=" sign ?
So that you can store multiple sessions states in one file, just as the
documentation says.
Xho
--
-------------------- http://NewsReader.Com/ --------------------
Usenet Newsgroup Service $9.95/Month 30GB
.
- Follow-Ups:
- Re: CGI.pm parsing odity
- From: FrankB
- Re: CGI.pm parsing odity
- References:
- CGI.pm parsing odity
- From: FrankB
- CGI.pm parsing odity
- Prev by Date: Re: Problem with Win32::API and pointers
- Next by Date: Re: CGI.pm parsing odity
- Previous by thread: CGI.pm parsing odity
- Next by thread: Re: CGI.pm parsing odity
- Index(es):