Re: Proposed FormVariables hierarchy
This WebDNA talk-list message is from 2000
It keeps the original formatting.
numero = 31584
interpreted = N
texte = On 8/5/2000 9:04, GHulbert@smithmicro.com said:>A proposed new hierarchy might go something like this: > >HTML Form Context (all passed-in form variables, smart [CART], >insecure text vars) > Application Context (things like [VERSION] [DATE] [TIME] >[ELAPSEDTIME], default secure text vars) > Browser Context (things like [IPADDRESS] [REFERRER] [USERNAME] >[PASSWORD]) > template code (your own contexts nested however you decide) > [xxx] <- look for xxx here, and if not found, go up ^^^ > >By adding a second namespace for holding text variables (up in the >HTML Form Context), we can provide a place for storing insecure text >variables. The parser will find secure text variables first, then >form variables, then insecure textvariables. A side-effect would be >that one could have text variables with exactly the same name in both >namespaces, but secure ones would be found first.This looks fine to me, and it sounds like the different name spaces are kept separate, but how would we access the other name spaces? Are they just lost to us? Or will we have something tricky like (for a variable x)
I hate to say it, but ASP's Request.Value(x) is starting to look good...I'd also like to see a more formal distinction between some of the layers, eg form variables are actually more local that insecure variables, so that makes your highest layer actually two layers. Thomas Wedderburn-Bisshop CIO, Woomera Net Solutions www.woomeranet.com.au Sydney, Australia Phone +61 2 9633 5048 fax +61 2 9633 5248 ############################################################# This message is sent to you because you are subscribed to the mailing list . To unsubscribe, E-mail to: To switch to the DIGEST mode, E-mail to To switch to the INDEX mode, E-mail to Send administrative queries to
Associated Messages, from the most recent to the oldest:
On 8/5/2000 9:04, GHulbert@smithmicro.com said:>A proposed new hierarchy might go something like this: > >HTML Form Context (all passed-in form variables, smart [cart], >insecure text vars) > Application Context (things like [version] [date] [time] >[elapsedtime], default secure text vars) > Browser Context (things like [ipaddress] [referrer] [username] >[password]) > template code (your own contexts nested however you decide) > [xxx] <- look for xxx here, and if not found, go up ^^^ > >By adding a second namespace for holding text variables (up in the >HTML Form Context), we can provide a place for storing insecure text >variables. The parser will find secure text variables first, then >form variables, then insecure textvariables. A side-effect would be >that one could have text variables with exactly the same name in both >namespaces, but secure ones would be found first.This looks fine to me, and it sounds like the different name spaces are kept separate, but how would we access the other name spaces? Are they just lost to us? Or will we have something tricky like (for a variable x) I hate to say it, but ASP's Request.Value(x) is starting to look good...I'd also like to see a more formal distinction between some of the layers, eg form variables are actually more local that insecure variables, so that makes your highest layer actually two layers. Thomas Wedderburn-Bisshop CIO, Woomera Net Solutions www.woomeranet.com.au Sydney, Australia Phone +61 2 9633 5048 fax +61 2 9633 5248 ############################################################# This message is sent to you because you are subscribed to the mailing list . To unsubscribe, E-mail to: To switch to the DIGEST mode, E-mail to To switch to the INDEX mode, E-mail to Send administrative queries to
Thomas Wedderburn-Bisshop
DOWNLOAD WEBDNA NOW!
Top Articles:
Talk List
The WebDNA community talk-list is the best place to get some help: several hundred extremely proficient programmers with an excellent knowledge of WebDNA and an excellent spirit will deliver all the tips and tricks you can imagine...
Related Readings:
SQL Madness (2005)
OT: need bad code (2005)
no template caching (1997)
Webcat 2.0.1 date math bug -> Crash! (1997)
question... no field names? (2002)
Math, Multiple Equasions and Show/Hide (1998)
Poll Please (2002)
WebCommerce: Folder organization ? (1997)
Sendmail: bounced e-mails (2001)
Stopping bad HTML propagation ? (1997)
Webcatalog/ColdFusion/Tango (1998)
re: How can I record purchases to a database? (1998)
WebDNA with WebStar V (2003)
A Couple Photos from the SmithMicro Booth at MacWorld (2000)
WebCat b13 CGI -shownext- (1997)
using showpage and showcart commands (1996)
Multiple ShipTo Addresses (2003)
Using [Include] Context (1999)
[interpret] inside the db field? (1997)
[WebDNA] MD5 Hash issue (2009)