Re: [WebDNA] WebDNA future
This WebDNA talk-list message is from 2010
It keeps the original formatting.
numero = 104459
interpreted = N
texte = Hi Brian, My understanding is that you'll have to duplicate your shared db's and repositories by making a copy for each domain, assuming of course that you want to go the FastCGI route rather than continuing with the regular version of WebDNA. I think WSC will not be supporting the regular version after 6.2.1 comes out though, so for the long term future you might miss out on specific features added to the FastCGI version but not the regular version. I'm just theorizing about this of course, so I'm going to wait for Chris to confirm or deny these assumptions, but if I'm not mistaken this is his general concept. Sincerely, Kenneth Grome www.KenGrome.com > Chris - > > I am not particularly familiar with how the fastCGI version will operate vs. the module version. Can you give a quick rundown on this? > > In my particular usage, I typically run multiple domains on the same physical server, sharing extensive function libraries and db repositories stored in globals. How will this change using fastCGI? > > Note that this is key to my future use of WebDNA, as I am constantly defending the use of such a "non-standard" technology as the core of our company's services. There is considerable pressure to move to a different platform, despite the 8 years of development time that has gone into our current systems. > > Brian Fries > BrainScan Software
Associated Messages, from the most recent to the oldest:
Hi Brian, My understanding is that you'll have to duplicate your shared db's and repositories by making a copy for each domain, assuming of course that you want to go the FastCGI route rather than continuing with the regular version of WebDNA. I think WSC will not be supporting the regular version after 6.2.1 comes out though, so for the long term future you might miss out on specific features added to the FastCGI version but not the regular version. I'm just theorizing about this of course, so I'm going to wait for Chris to confirm or deny these assumptions, but if I'm not mistaken this is his general concept. Sincerely, Kenneth Grome www.KenGrome.com > Chris - > > I am not particularly familiar with how the fastCGI version will operate vs. the module version. Can you give a quick rundown on this? > > In my particular usage, I typically run multiple domains on the same physical server, sharing extensive function libraries and db repositories stored in globals. How will this change using fastCGI? > > Note that this is key to my future use of WebDNA, as I am constantly defending the use of such a "non-standard" technology as the core of our company's services. There is considerable pressure to move to a different platform, despite the 8 years of development time that has gone into our current systems. > > Brian Fries > BrainScan Software
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:
[addlineitems] display (1997)
WebCat2.0 acgi vs plugin (1997)
Summary search -- speed (1997)
(1997)
Press Release hit the NewsWire!!! (1997)
PSC recommends what date format yr 2000??? (1997)
Weird problems with [SHOWIF]s (1997)
attn: smitmicro - cart limitation (2002)
More on the email templates (I like it) (1997)
[ipaddress] (2003)
using showpage and showcart commands (1996)
Anomaly ? causes NT application event log to overflow (1997)
[WebDNA] Who and what is ZIRCOM (2018)
Calendar using WebCatalog? (1997)
SandBox and ImageMagick (2003)
Caching [include] files ... (1997)
[WriteFile] problems (1997)
autosensing lanague selection (1997)
ConverChars (1999)
suffix mapping for NT? (1997)