Re: [WebDNA] Just drop the Server version
This WebDNA talk-list message is from 2015
It keeps the original formatting.
numero = 112098
interpreted = N
texte = Getting rid of the server version makes WebDNA a less attractive = language.=20 Let me explain. WebDNA=92s databases system is very easy to use for web = programmers of simple to moderate web sites. It starts to fall off the = rails a little as web projects get bigger, but for those of us that love = the simplicity of WebDNA, we find ways to make it work (using the = globals folder to have path agnostic databases, sharding databases to = make them small and speedy, etc)=20 My understanding of the FCGI is it starts a process and loads into = memory the databases it needs for 1 domain(website). Multiple instances = of the FCI to support multiple front ends for one set of databases (via = a shared universal globals folder (is that even possible with the FCGI?) = would cause all sorts of data inconsistency problems.=20 Brian B. Burton > On Feb 10, 2015, at 10:01 AM, Kenneth Grome
= wrote: >=20 > Hi tom, >=20 > Fortunately you have a brand new Server version 8.0.2 that works > for you now, and I suspect that this version will hold you for > another 5-10 years, even if no new Server version were ever > developed or released, correct? >=20 > Another issue here is that if WSC would make "^" work in the > FastCGI version (the way it works in the Server version) you'd be > able to run the FastCGI version for your CMS, correct? >=20 > When I suggested no more development on the Server version I was > offering a supporting option for Chris' goal when he said: >=20 > "We want to keep things as simple as possible." >=20 > One way to dramatically simplify WSC's software development work > (and save a ton of money) is to stop developing all versions > except one. And since the FastCGI version runs on the most > popular servers on the web these days, it would seem to "make > sense" to continue to develop only the FastCGI version. >=20 > I think Chris has finally gotten WSC back on-track for success > again. We are certainly seeing more development now than during > the previous two or three years! I would hate to see all this new > development 'disappear' because the company tries to stretch their > resources too thin. >=20 > This is a hard decision, I know, but sometimes hard decisions must > be made in order for a company to survive. And I for one would > like to see the company not just survive but thrive! >=20 > 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:
Getting rid of the server version makes WebDNA a less attractive = language.=20 Let me explain. WebDNA=92s databases system is very easy to use for web = programmers of simple to moderate web sites. It starts to fall off the = rails a little as web projects get bigger, but for those of us that love = the simplicity of WebDNA, we find ways to make it work (using the = globals folder to have path agnostic databases, sharding databases to = make them small and speedy, etc)=20 My understanding of the FCGI is it starts a process and loads into = memory the databases it needs for 1 domain(website). Multiple instances = of the FCI to support multiple front ends for one set of databases (via = a shared universal globals folder (is that even possible with the FCGI?) = would cause all sorts of data inconsistency problems.=20 Brian B. Burton > On Feb 10, 2015, at 10:01 AM, Kenneth Grome = wrote: >=20 > Hi tom, >=20 > Fortunately you have a brand new Server version 8.0.2 that works > for you now, and I suspect that this version will hold you for > another 5-10 years, even if no new Server version were ever > developed or released, correct? >=20 > Another issue here is that if WSC would make "^" work in the > FastCGI version (the way it works in the Server version) you'd be > able to run the FastCGI version for your CMS, correct? >=20 > When I suggested no more development on the Server version I was > offering a supporting option for Chris' goal when he said: >=20 > "We want to keep things as simple as possible." >=20 > One way to dramatically simplify WSC's software development work > (and save a ton of money) is to stop developing all versions > except one. And since the FastCGI version runs on the most > popular servers on the web these days, it would seem to "make > sense" to continue to develop only the FastCGI version. >=20 > I think Chris has finally gotten WSC back on-track for success > again. We are certainly seeing more development now than during > the previous two or three years! I would hate to see all this new > development 'disappear' because the company tries to stretch their > resources too thin. >=20 > This is a hard decision, I know, but sometimes hard decisions must > be made in order for a company to survive. And I for one would > like to see the company not just survive but thrive! >=20 > Regards, > Kenneth Grome > WebDNA Solutions > http://www.webdnasolutions.com > Web Database Systems and Linux Server Management
Brian Burton
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:
Can [writefile] files be served thru webcat? (2000)
Simple way to create unique SKU (1997)
Announce: New WebCatalog Site (1998)
Serving images from databases (1998)
referrer and no caches (1997)
Almost a there but..bye bye NetCloak (1997)
Applescript, WebDNA, and PDF (1997)
problems with WebCat-Plugin ()
Can't use old cart file (was One more try) (1997)
I give up!! (1997)
Exclamation point (1997)
[OT] MacOs IE5 topmargin and leftmargin bug (2000)
Adding multiple items to Cart at one time, & append context problem (1998)
WebCat2b13 Mac plugin - [sendmail] and checkboxes (1997)
Security Question (1997)
Secure Server basic question... (1997)
NT Processor Woes (2000)
FREE Stuff .. (2003)
Summing fields (1997)
Detecting NULL value in returned SQL (2000)