[WebDNA] Just drop the Server version

This WebDNA talk-list message is from

2015


It keeps the original formatting.
numero = 112082
interpreted = N
texte = > Using the old "^" to access the user global directory for > WebDNA server and the /WebDNA directory (or a new /global one) > would imply different code for both versions. How different could it be? Can't you just make the code identical in both versions by having it look in the prefs for the globals folder location? Then you do not have to hard-code its path, and we gain the flexibility of being able to put the globals folder wherever we want it. Or do other issues come into play here? > We want to keep things as simple as possible. If this issue is bigger or more complex than just the globals folder path, maybe it's time to consider the possibility of stopping all development on the Server version. Then it won't get in the way of your giving us the features we request in the FastCGI version -- which is probably an order of magnitude easier to support and maintain anyways. Sorry if this suggestion sounds like heresy from a long-time user, but I actually want "^" to refer to a globals folder in the FastCGI version and I don't care what it takes to make it work. So if it's too much hassle or expense to support this requested feature by making the code identical in both versions, I say: "Just kill the Server version!" I would rather see WebDNA survive and thrive with only the FastCGI version than to see it fail because you tried to support both versions without enough resources. Don't get me wrong here. I think you should still continue to sell the existing Server version for backward compatibility to those who want it. All I'm suggesting is that you "freeze" the Server version now and forever more. Then you will have only the FastCGI version of code to write and maintain, and any new feature we request will not have to consider how the internal code in the old Server version might be different. Retire the Server version and everything becomes MUCH SIMPLER! That's my thought for the day ... :) Regards, Kenneth Grome WebDNA Solutions http://www.webdnasolutions.com Web Database Systems and Linux Server Management Associated Messages, from the most recent to the oldest:

    
  1. Re: [WebDNA] Just drop the Server version (Michael Davis 2015)
  2. Re: [WebDNA] Just drop the Server version (Dan Strong 2015)
  3. Re: [WebDNA] Just drop the Server version ("Matthew A Perosi, Psi Prime" 2015)
  4. Re: [WebDNA] Just drop the Server version (Palle 2015)
  5. Re: [WebDNA] Just drop the Server version (Kenneth Grome 2015)
  6. Re: [WebDNA] Just drop the Server version (christophe.billiottet@webdna.us 2015)
  7. Re: [WebDNA] Just drop the Server version (Brian Burton 2015)
  8. Re: [WebDNA] Just drop the Server version (Kenneth Grome 2015)
  9. Re: [WebDNA] Just drop the Server version (Tom Duke 2015)
  10. [WebDNA] Just drop the Server version (Kenneth Grome 2015)
> Using the old "^" to access the user global directory for > WebDNA server and the /WebDNA directory (or a new /global one) > would imply different code for both versions. How different could it be? Can't you just make the code identical in both versions by having it look in the prefs for the globals folder location? Then you do not have to hard-code its path, and we gain the flexibility of being able to put the globals folder wherever we want it. Or do other issues come into play here? > We want to keep things as simple as possible. If this issue is bigger or more complex than just the globals folder path, maybe it's time to consider the possibility of stopping all development on the Server version. Then it won't get in the way of your giving us the features we request in the FastCGI version -- which is probably an order of magnitude easier to support and maintain anyways. Sorry if this suggestion sounds like heresy from a long-time user, but I actually want "^" to refer to a globals folder in the FastCGI version and I don't care what it takes to make it work. So if it's too much hassle or expense to support this requested feature by making the code identical in both versions, I say: "Just kill the Server version!" I would rather see WebDNA survive and thrive with only the FastCGI version than to see it fail because you tried to support both versions without enough resources. Don't get me wrong here. I think you should still continue to sell the existing Server version for backward compatibility to those who want it. All I'm suggesting is that you "freeze" the Server version now and forever more. Then you will have only the FastCGI version of code to write and maintain, and any new feature we request will not have to consider how the internal code in the old Server version might be different. Retire the Server version and everything becomes MUCH SIMPLER! That's my thought for the day ... :) Regards, Kenneth Grome WebDNA Solutions http://www.webdnasolutions.com Web Database Systems and Linux Server Management 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:

WebCatalog2 Feature Feedback (1996) Image download problem (2001) installing webcatalog problem. HELP! (1998) Discounts: Buy One, Get One =?ISO-8859-1?Q?99=A2?= (2004) MATH (1998) Need relative path explanation (1997) 4.5.1 (2003) math a various prices (1997) sorting and grouping (1998) [OT] Am I an Idiot? (2004) Quantity/price formula (1998) WebCat2b13MacPlugin - [math][date][/math] problem (1997) [WebDNA] max in a search (2009) Alternating colors (1997) Webcatalog and foreign languages (1998) Webcatalog error, Plug-in for Webstar (1996) os 8.5 (1999) why won't this work, please tell me??? (2001) A question on sub-categories (1997) ANN: Strategic Partnership with BuyStream Announced. (2000)