Re: WC2.0 Memory Requirements

This WebDNA talk-list message is from

1997


It keeps the original formatting.
numero = 10263
interpreted = N
texte = >I'm a bit confused about this - I prefer to run plugins but can Webstar SSL >use the same plugins folder as Webstar. I presumed not so I'm using the cgi >to be accessed by both.I prefer plugins too, but right now WebStar/SSL looks for plugins in a completely different folder. Which means you get 2 instances of WebCatalog plugin running when you only want one. Until we implement the complex workaround Chuck is asking us to do, I recommend you use the CGI instead, (important only in an SSL environment).You can make the CGI act like a plugin by simply defining an ACTION for it the same way you would with a plugin. Remember to define the ACTION in both W* and W*/SSL's preferences.>This raises the problem of how I use the same cgi on different multihomed >sites on the same server. Using the plugin there's no path to worry about.I'm guessing that if you define the ACTION for the CGI there will be no path to worry about there, either.Grant Hulbert, V.P. Engineering | Tools for WebWarriors Pacific Coast Software | WebCatalog, WebCommerce Solution 11770 Bernardo Plaza Court, #462 | SiteEdit, SiteCheck, PhotoMaster San Diego, CA 92128 | 619/675-1106 Fax: 619/675-0372 | http://www.smithmicro.com Associated Messages, from the most recent to the oldest:

    
  1. Re: WC2.0 Memory Requirements (Grant Hulbert 1997)
  2. Re: WC2.0 Memory Requirements (Rob Schmidt 1997)
  3. Re: WC2.0 Memory Requirements (Grant Hulbert 1997)
  4. WC2.0 Memory Requirements (plake 1997)
>I'm a bit confused about this - I prefer to run plugins but can Webstar SSL >use the same plugins folder as Webstar. I presumed not so I'm using the cgi >to be accessed by both.I prefer plugins too, but right now WebStar/SSL looks for plugins in a completely different folder. Which means you get 2 instances of WebCatalog plugin running when you only want one. Until we implement the complex workaround Chuck is asking us to do, I recommend you use the CGI instead, (important only in an SSL environment).You can make the CGI act like a plugin by simply defining an ACTION for it the same way you would with a plugin. Remember to define the ACTION in both W* and W*/SSL's preferences.>This raises the problem of how I use the same cgi on different multihomed >sites on the same server. Using the plugin there's no path to worry about.I'm guessing that if you define the ACTION for the CGI there will be no path to worry about there, either.Grant Hulbert, V.P. Engineering | Tools for WebWarriors Pacific Coast Software | WebCatalog, WebCommerce Solution 11770 Bernardo Plaza Court, #462 | SiteEdit, SiteCheck, PhotoMaster San Diego, CA 92128 | 619/675-1106 Fax: 619/675-0372 | http://www.smithmicro.com Grant Hulbert

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:

Calculating UPS Shipping (1999) RE: PDF (1999) multi-paragraph fields (1997) PCS Frames (1997) Multiple Pulldowns (1997) multiple prices (1998) [OT] WebDNA and MyODBC (2003) Re[2]: 2nd WebCatalog2 Feature Request (1996) Before I Can Begin . . . (1998) [sendmail] on NT? (1997) Random question (1998) time and welcome (1999) founditems (2000) Sorting by date (1997) If Empty ? (1997) WebCat2b13MacPlugIn - syntax to convert date (1997) webcatalog and webmerchant 2.1 (1998) General Purpose Database utility ????? (2003) [WebDNA] LowRam (2012) [SHOWIF] (1997)