Re: [WebDNA] WebDNA future
This WebDNA talk-list message is from 2010
It keeps the original formatting.
numero = 104467
interpreted = N
texte = >> The fastCGI has shell access if the administrator provides shell = access to the user. On the contrary to the module version which needs = the same permissions as apache (to be able to interact with apache = files), a CGI runs with a single website permissions. This allows a = webmaster to limit the range of the application, which will not be = allowed to interact with other websites files. This greatly improves the = security compared to the module. >=20 >=20 > Chris, can you explain what you mean by "if an admin provides shell = access to the user"? That is what WebDNA does... so not sure what you = mean. When you chose your hosting provider, some will allow shell access to = the website, others will disable it. WebDNA will not be able to use = shell access if the website has shell disabled. >>> Also, I personally utilize a lot of the (extended) features of the = module based app.. globals and sandboxes in particular.. so I personally = don't want to see those go away in the module-based app. >> Because of the very core of the fastCGI, there will be no need for = globals or sandboxes: every single website owner will have full control = over his WebDNA fastCGI copy, license included. No need for a "part" = administration, or a central repository of functions. >> - chris--------------------------------------------------------- >=20 >=20 > O.K., but if you notice, I was talking about the module-based app. = Will it still contain a globals directory? yes. - chris
Associated Messages, from the most recent to the oldest:
>> The fastCGI has shell access if the administrator provides shell = access to the user. On the contrary to the module version which needs = the same permissions as apache (to be able to interact with apache = files), a CGI runs with a single website permissions. This allows a = webmaster to limit the range of the application, which will not be = allowed to interact with other websites files. This greatly improves the = security compared to the module. >=20 >=20 > Chris, can you explain what you mean by "if an admin provides shell = access to the user"? That is what WebDNA does... so not sure what you = mean. When you chose your hosting provider, some will allow shell access to = the website, others will disable it. WebDNA will not be able to use = shell access if the website has shell disabled. >>> Also, I personally utilize a lot of the (extended) features of the = module based app.. globals and sandboxes in particular.. so I personally = don't want to see those go away in the module-based app. >> Because of the very core of the fastCGI, there will be no need for = globals or sandboxes: every single website owner will have full control = over his WebDNA fastCGI copy, license included. No need for a "part" = administration, or a central repository of functions. >> - chris--------------------------------------------------------- >=20 >=20 > O.K., but if you notice, I was talking about the module-based app. = Will it still contain a globals directory? yes. - chris
christophe.billiottet@webdna.us
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:
WebDNA-Talk Digest mode broken (1997)
Cart # Starting at 1000 (2000)
choice of images (2000)
Multiple Ad databases? (1997)
[isfile] ? (1997)
Newbie: ASIP vs WebTen? (2000)
UPS Calculator (2003)
FAX orders (1996)
Rams SuperBowl Champs (2000)
database paths/names, and a typo (1997)
[WebDNA] Convert db to MySQL (2009)
Error Log.db --however (1997)
Error 11 (1996)
[WriteFile] problems (1997)
Field validation problem (1999)
Only charge card when product shipped ? (1997)
Am I going senile? (Price recalc based on quantity) (1997)
customizing the color of user's pages (1997)
OT - help.. (2003)
Authentication (1998)