Re[5]: Problem with new formvariables

This WebDNA talk-list message is from

2000

It keeps the original formatting. numero = 31241
interpreted = N
texte = And how would the new security model affect you then. You can still testwhether any variables were passed on the command line and branch accordingly. The only thing that you could not do is have a variable passed on the commandline overload a variable defined in the template itself.vis. for the following testpage.tpl?myvar=yes[if [myvar]=[raw][myvar][/raw][!] they did not include the variable[/!][if [myvar]=yes][!]they did and it equalled yes[/!][text]myvar=no[/text][myvar][!]this is now no not yes[/!]Does that clear things up any? Can you tell me how your code works that thiswould break?John Peacock____________________Reply Separator____________________Subject: Re[4]: Problem with new formvariables Author: Date: 5/2/2000 11:45 AM>Grant ->>That is exactly why the is a better idea; >you just need a single branch at the top of the parser (old vs new). >If you allow any number of variable to be insecure, you will need to >have a much more complicated>parser. By going all or nothing with the above tag, you can simply >keep the old parse code in parallel with the new with a single >branch.John,Just a thought but it sounds as if your idea will keep me from using any new features of 4.0 as long as I want to keep to the 3.0 hierarchy. I would think it be more important to find a way to blend the functionality the current logic provides while improving the default security.Good, bad or indifferent I use the current hierarchy to present different data based on the variables passed to the page. It is a great feature of WebCatalog. Close the security hole but let me use this same feature.Grant, my vote is for default to secure but allow me to set unsecure (overridden by form variables) text/math variables.Thanks,-- Sam Lewis, V.P. TechnologyTehabi Books http://www.tehabi.com/1201 Camino Del Mar, Suite 100, Del Mar, CA 92014Tel: 626-852-0956 Fax: 916-404-5698 mailto:Sam@tehabi.com#############################################################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:

Re[5]: Problem with new formvariables (jpeacock@univpress.com 2000)

And how would the new security model affect you then. You can still testwhether any variables were passed on the command line and branch accordingly. The only thing that you could not do is have a variable passed on the commandline overload a variable defined in the template itself.vis. for the following testpage.tpl?myvar=yes[if [myvar]=[raw][myvar][/raw][!] they did not include the variable[/!][if [myvar]=yes][!]they did and it equalled yes[/!][text]myvar=no[/text][myvar][!]this is now no not yes[/!]Does that clear things up any? Can you tell me how your code works that thiswould break?John Peacock____________________Reply Separator____________________Subject: Re[4]: Problem with new formvariables Author: Date: 5/2/2000 11:45 AM>Grant ->>That is exactly why the is a better idea; >you just need a single branch at the top of the parser (old vs new). >If you allow any number of variable to be insecure, you will need to >have a much more complicated>parser. By going all or nothing with the above tag, you can simply >keep the old parse code in parallel with the new with a single >branch.John,Just a thought but it sounds as if your idea will keep me from using any new features of 4.0 as long as I want to keep to the 3.0 hierarchy. I would think it be more important to find a way to blend the functionality the current logic provides while improving the default security.Good, bad or indifferent I use the current hierarchy to present different data based on the variables passed to the page. It is a great feature of WebCatalog. Close the security hole but let me use this same feature.Grant, my vote is for default to secure but allow me to set unsecure (overridden by form variables) text/math variables.Thanks,-- Sam Lewis, V.P. TechnologyTehabi Books http://www.tehabi.com/1201 Camino Del Mar, Suite 100, Del Mar, CA 92014Tel: 626-852-0956 Fax: 916-404-5698 mailto:Sam@tehabi.com#############################################################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 jpeacock@univpress.com

DOWNLOAD WEBDNA NOW!

Re[5]: Problem with new formvariables

2000

Top Articles:

Related Readings: