Re: where to put code

This WebDNA talk-list message is from

1998


It keeps the original formatting.
numero = 19316
interpreted = N
texte = Thanks Peter. The long URL problem with the security issue was one reason I was using more forms rather than links. But maybe I should just put stuff on the resulting page. I'll have to give that more thought. >Unfortunately the manual gives no comments about advantages and >disadvantages in a clear manner. Basicly we can put the code where we want >to. > >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. > > >Peter. > >__________________________________________ >Peter Ostry - po@ostry.com - www.ostry.com >Ostry & Partner - Ostry Internet Solutions >Auhofstrasse 29 A-1130 Vienna Austria >fon ++43-1-8777454 fax ++43-1-8777454-21 > Associated Messages, from the most recent to the oldest:

    
  1. Re: where to put code (Paul Uttermohlen 1998)
  2. Re: where to put code (Charles Kefauver 1998)
  3. Re: where to put code (Dave MacLeay 1998)
  4. Re: where to put code (Peter Ostry 1998)
  5. Re: where to put code (Charles Kefauver 1998)
  6. Re: where to put code (Kenneth Grome 1998)
  7. Re: where to put code (Kenneth Grome 1998)
  8. Re: where to put code (Kevin Furuta 1998)
  9. Re: where to put code (John Hill 1998)
  10. Re: where to put code (Sue Ann Sanders 1998)
  11. Re: where to put code (Sue Ann Sanders 1998)
  12. Re: where to put code (Peter Ostry 1998)
  13. Re: where to put code (Kenneth Grome 1998)
  14. where to put code (Sue Ann Sanders 1998)
Thanks Peter. The long URL problem with the security issue was one reason I was using more forms rather than links. But maybe I should just put stuff on the resulting page. I'll have to give that more thought. >Unfortunately the manual gives no comments about advantages and >disadvantages in a clear manner. Basicly we can put the code where we want >to. > >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. > > >Peter. > >__________________________________________ >Peter Ostry - po@ostry.com - www.ostry.com >Ostry & Partner - Ostry Internet Solutions >Auhofstrasse 29 A-1130 Vienna Austria >fon ++43-1-8777454 fax ++43-1-8777454-21 > Sue Ann Sanders

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:

Read and weep (2003) Multiple Newcarts (1996) PIXO support (1997) searching for items that begin with a number (2004) two unique banners on one page (1997) WebCat2b15MacPlugin - [protect] (1997) Error:Too many nested [xxx] contexts (1997) unsubscribe (1997) Anyone running CommuniGate (2001) Encrypt/Decrypt (2007) Sorting Numbers (1997) question: webmerchant connection (1997) pictures / referrer etc. (1998) Webcat 4.0.1b2 on ftp - what does it fix? (2000) Cart Number sequence (1997) Date search - yes or no (1997) [showif] / [hideif] (1997) Date Formats (1997) Adding up line items. (2000) Using [Include] Context (1999)