[ CC'ed to the mailing list ]
Tom Brown wrote:
>> You could create some "macros" to make things easier, like:
>>
>> proc hidden {key val} {
>> puts "<input ... name = $key val = $val ....>"
>> }
>>
>> Keep in mind that someone could observe what's happening and substitute
>> their own values for things passed through their browser.
>
>
> Must I use <form action="filename.rvt"> for the <input...> tag to pass
> the variables to a document?
It depends on how your page is structured. You can also create url's
like so:
puts "<a href=\"/foo.rvt?foovar=$foo&othervar=$val\">Click here!</a>"
although it's best to use the http::formatQuery proc to do this cleanly
and safely.
>> Not really. The web is stateless, and making web apps stateful is a
>> pain in the neck. You can use a database instead of a flat file - that
>> buys you something in terms of speed and reliability, but the concept is
>> pretty much the same.
> Do I need to save session info so that different browser sessions read
> their own database record and not another's?
I think the session package takes care of things for you via cookies so
that you get the right session, but I haven't used it myself...
--
David N. Welton
- http://www.dedasys.com/davidw/
Linux, Open Source Consulting
- http://www.dedasys.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
