Re: Using Applescript to process WebCatalog functions

This WebDNA talk-list message is from

1998


It keeps the original formatting.
numero = 17704
interpreted = N
texte = >Anyway - the new WebCat plugin does not need AppleScript. >You should turn off AppleScript on your webserver, for security and performance... This is simply not true!There are many functions that a MAc webmaster may needd to perform that simply cannot perform without AppleScript. And there are existing WebDNA modules on the market that *require* AppleScript ...The first example that occurs to me -- and one that many Mac webmasters are using -- is the WebDNA-powered Rumpus Admin module. It relies on an embedded AppleScript to send an AppleEvent to Rumpus. If you get rid of AppleScript, that AppleEvent will not be sent, and Rumpus will not reload it's newly-updated database file ... and the result will be a Rumpus Admin module that doesn't work!So please do NOT get rid of AppleScript without understanding exactly what effect that action is going to have on the rest of your system. These are the facts:1- WebCatalog needs AppleScript to send AppleEvents to other applications. 2- WebCatalog duplicates very few of the tasks AppleScript can perform. 3- There are many tasks AppleScript can perform that WebCatalog cannot.Sincerely, Ken Grome 808-737-6499 WebDNA Solutions mailto:ken@webdna.net http://www.webdna.net Associated Messages, from the most recent to the oldest:

    
  1. Re: Using Applescript to process WebCatalog functions (Mike Heininger 1998)
  2. Re: Using Applescript to process WebCatalog functions (Peter Ostry 1998)
  3. Re: Using Applescript to process WebCatalog functions (Kenneth Grome 1998)
  4. Re: Using Applescript to process WebCatalog functions (Britt T. 1998)
  5. Re: Using Applescript to process WebCatalog functions (Peter Ostry 1998)
  6. Re: Using Applescript to process WebCatalog functions (Britt T. 1998)
  7. Re: Using Applescript to process WebCatalog functions (Peter Ostry 1998)
  8. Re: Using Applescript to process WebCatalog functions (Britt T. 1998)
  9. Re: Using Applescript to process WebCatalog functions (Peter Ostry 1998)
  10. Re: Using Applescript to process WebCatalog functions (Kenneth Grome 1998)
  11. Re: Using Applescript to process WebCatalog functions (Peter Ostry 1998)
  12. Re: Using Applescript to process WebCatalog functions (Bob Mosebar 1998)
  13. Re: Using Applescript to process WebCatalog functions (Peter Ostry 1998)
  14. Re: Using Applescript to process WebCatalog functions (Peter Ostry 1998)
  15. Re: Using Applescript to process WebCatalog functions (Bob Mosebar 1998)
  16. Re: Using Applescript to process WebCatalog functions (Kenneth Grome 1998)
  17. Re: Using Applescript to process WebCatalog functions (Kenneth Grome 1998)
  18. Re: Using Applescript to process WebCatalog functions (Kenneth Grome 1998)
  19. Re: Using Applescript to process WebCatalog functions (Peter Ostry 1998)
  20. Re: Using Applescript to process WebCatalog functions (Bob Mosebar 1998)
  21. Re: Using Applescript to process WebCatalog functions (Bob Mosebar 1998)
  22. Re: Using Applescript to process WebCatalog functions (Britt T. 1998)
  23. Re: Using Applescript to process WebCatalog functions (Peter Ostry 1998)
  24. Re: Using Applescript to process WebCatalog functions (Kenneth Grome 1998)
  25. Re: Using Applescript to process WebCatalog functions (Peter Ostry 1998)
  26. Re: Using Applescript to process WebCatalog functions (Bob Mosebar 1998)
  27. Re: Using Applescript to process WebCatalog functions (Kenneth Grome 1998)
  28. Re: Using Applescript to process WebCatalog functions (Kenneth Grome 1998)
  29. Re: Using Applescript to process WebCatalog functions (PCS Technical Support 1998)
  30. Re: Using Applescript to process WebCatalog functions (Peter Ostry 1998)
  31. Using Applescript to process WebCatalog functions (Bob Mosebar 1998)
>Anyway - the new WebCat plugin does not need AppleScript. >You should turn off AppleScript on your webserver, for security and performance... This is simply not true!There are many functions that a MAc webmaster may needd to perform that simply cannot perform without AppleScript. And there are existing WebDNA Modules on the market that *require* AppleScript ...The first example that occurs to me -- and one that many Mac webmasters are using -- is the WebDNA-powered Rumpus Admin module. It relies on an embedded AppleScript to send an AppleEvent to Rumpus. If you get rid of AppleScript, that AppleEvent will not be sent, and Rumpus will not reload it's newly-updated database file ... and the result will be a Rumpus Admin module that doesn't work!So please do NOT get rid of AppleScript without understanding exactly what effect that action is going to have on the rest of your system. These are the facts:1- WebCatalog needs AppleScript to send AppleEvents to other applications. 2- WebCatalog duplicates very few of the tasks AppleScript can perform. 3- There are many tasks AppleScript can perform that WebCatalog cannot.Sincerely, Ken Grome 808-737-6499 WebDNA Solutions mailto:ken@webdna.net http://www.webdna.net 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:

creating files dynamically (2002) Format 1.15 to 1:15:00 or 01:15:00 (2002) PCS Frames (1997) WebCat for Site Search? (1997) Make sure I understand this??? (1997) Too Much In (1998) Multi Colonns (1998) Still having math problems (1997) Undeliverable Mail (1997) totals (1997) [protect] on NT? (1997) Trouble starting WC under OSX (2001) Sendmail Excel attachment (2003) read and write you own cookies with webcat (1997) Values to Thankyou page lost? (1998) [date] tag not working on mac 4.0.1 (2000) RE: is sku a REQUIRED field on NT (1997) AccountAuthorizer doesn't seem to work (1997) Satisfy Me ! was: Why can't support be satisfying to (2000) WebCatalog/WebMerchant 2.1 (1998)