Re: where to put code

This WebDNA talk-list message is from

1998

It keeps the original formatting. numero = 19322
interpreted = N
texte = >>>In some of the samples I've seen sometimes the WebDNA code is within the>>>HyperLInk, sometimes in hidden form fields and sometimes in the file that>>>is returned.>>Unfortunately the manual gives no comments about advantages and>disadvantages in a clear manner.Well, you're right about that.>I personally prefer to use the context method on resulting pages. There I>can see the code at once, which makes it easier to understand. Anyway - I>do not like these long ugly URL's... And if one uses Replace or Delete>in a link, then this command has to be allowed for user input and therefore>some funny guy can destroy the database by simply playing with the URL.>There can be situation when commands in th URL make sense, but my personal>recommendation is to use contexts like [search...] on the target page>whenever you can.I agree. My technique, mainly for security reasons, is to use contexts all the time. I never put commands into my URLs, because then I can disable all commands, thereby making it impossible for people to send commands by typing them into the Location field in their browsers.Sincerely,Ken Grome808-737-6499WebDNA Solutionsmailto:ken@webdna.nethttp://www.webdna.net Associated Messages, from the most recent to the oldest:

Re: where to put code (Paul Uttermohlen 1998)
Re: where to put code (Charles Kefauver 1998)
Re: where to put code (Dave MacLeay 1998)
Re: where to put code (Peter Ostry 1998)
Re: where to put code (Charles Kefauver 1998)
Re: where to put code (Kenneth Grome 1998)
Re: where to put code (Kenneth Grome 1998)
Re: where to put code (Kevin Furuta 1998)
Re: where to put code (John Hill 1998)
Re: where to put code (Sue Ann Sanders 1998)
Re: where to put code (Sue Ann Sanders 1998)
Re: where to put code (Peter Ostry 1998)
Re: where to put code (Kenneth Grome 1998)
where to put code (Sue Ann Sanders 1998)

>>>In some of the samples I've seen sometimes the WebDNA code is within the>>>HyperLInk, sometimes in hidden form fields and sometimes in the file that>>>is returned.>>Unfortunately the manual gives no comments about advantages and>disadvantages in a clear manner.Well, you're right about that.>I personally prefer to use the context method on resulting pages. There I>can see the code at once, which makes it easier to understand. Anyway - I>do not like these long ugly URL's... And if one uses Replace or Delete>in a link, then this command has to be allowed for user input and therefore>some funny guy can destroy the database by simply playing with the URL.>There can be situation when commands in th URL make sense, but my personal>recommendation is to use contexts like [search...] on the target page>whenever you can.I agree. My technique, mainly for security reasons, is to use contexts all the time. I never put commands into my URLs, because then I can disable all commands, thereby making it impossible for people to send commands by typing them into the Location field in their browsers.Sincerely,Ken Grome808-737-6499WebDNA Solutionsmailto:ken@webdna.nethttp://www.webdna.net Kenneth Grome

DOWNLOAD WEBDNA NOW!

Re: where to put code

1998

Top Articles:

Related Readings: