Re: Hierarchy of form/text/math variables
This WebDNA talk-list message is from 2000
It keeps the original formatting.
numero = 31113
interpreted = N
texte = >I like the default to be more secure, so I would prefer a context >that would allow you to specify a chunk of code that would allow the >insecure behavior. > >Then you could: > >>
>> . >> . >> whatever code you needed >> . >> . >> > >everything else would use the new secure method. For old code, you >could make the whole page insecure by placing the context around the >whole page. Includes would have to have separate insecure tags. In order to remain backwards-compatible with all the existing webcat sites out there, I think the default should be insecure -- just like it's always been.I also believe that the issue here is the variables themselves, not how we can make them work differently in different parts of the page by using some new context. Can you imagine the debugging problems this would create?We don't need on-the-fly changes to our variable hierarchy, we just need a new level of variables that don't get overridden by formvariables -- and that's all we need. Jesse's suggestion seems far easier, far more flexible, and a lot easier to code -- not to mention a whole lot easier to debug. ================================ Kenneth Grome, WebDNA Consultant 808-737-6499 http://webdna.net ================================############################################################# 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:
>I like the default to be more secure, so I would prefer a context >that would allow you to specify a chunk of code that would allow the >insecure behavior. > >Then you could: > >> >> . >> . >> whatever code you needed >> . >> . >> > >everything else would use the new secure method. For old code, you >could make the whole page insecure by placing the context around the >whole page. Includes would have to have separate insecure tags. In order to remain backwards-compatible with all the existing webcat sites out there, I think the default should be insecure -- just like it's always been.I also believe that the issue here is the variables themselves, not how we can make them work differently in different parts of the page by using some new context. Can you imagine the debugging problems this would create?We don't need on-the-fly changes to our variable hierarchy, we just need a new level of variables that don't get overridden by formvariables -- and that's all we need. Jesse's suggestion seems far easier, far more flexible, and a lot easier to code -- not to mention a whole lot easier to debug. ================================ Kenneth Grome, WebDNA Consultant 808-737-6499 http://webdna.net ================================############################################################# 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
Kenneth Grome
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:
[OT] Theiving B*****ds (2004)
Encrypting userid for email (2000)
TRAINING videos - Prove IT. (1998)
[math] variable question (1997)
Fun with dates (1997)
WC TableGrinder (1997)
RE: Can a database get stomped by simultaneous access? (1997)
Snake Bites (1997)
RE: shrink-wrapped version out yet? (1997)
WC 2.0 frames feature (1997)
RE: WebCat: Access denied, but why? - The solution. (1997)
WebCat2: Found Items syntax, etc. (1997)
[ModDate] & [ModTime] ? (1997)
Mondo amounts of Mail [long] (1999)
combine search (1998)
Re:Formulas.db / Quantity Discount problem (1998)
Help with nested search (1998)
WebCat cannot handle compatible search parameters? (1997)
tracking no. of downloads (2006)
web merchant (2000)