Re: where to put code

This WebDNA talk-list message is from

1998


It keeps the original formatting.
numero = 19311
interpreted = N
texte = At 15:31 Uhr 04.08.1998, Sue Ann Sanders wrote: >>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. 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)
At 15:31 Uhr 04.08.1998, Sue Ann Sanders wrote: >>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. 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 Peter Ostry

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:

[BULK] [WebDNA] Anyone using WebDNA7 and Lion Server? (2011) For those of you not on the WebCatalog Beta... (1997) webcat pro (1998) [thisurl] or another way (2000) PIXO support (1997) [WebDNA] Some WebDNA news (2014) WebCatalog dying in NT (1998) problem: mail changed (1997) [WebDNA] Bug in decrypt method=Base64 (2012) time and welcome (1999) [WriteFile] problems (1997) I'm new be kind (1997) Date problems (1997) Search in 2 or more catalogs (1997) Problems mit mysql (2004) Roundup function? (1997) $flushcache causes crash (2000) New public beta available (1997) Search Sort Random (2004) can WC render sites out? (1997)