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:
More on the email templates (1997)
Setting variables. (1998)
Truncated value after space - refresh my memory.... (1997)
Re2: AAgghh!! Help, please. SSL strikes again. (1997)
[WebDNA] JSONStore Levels (2020)
multi-paragraph fields (1997)
SOP for WebDNA talk - MSNBot Crashing (2004)
PSC recommends what date format yr 2000??? (1997)
Validation (2000)
Aquick question about replace (1999)
Need help with emailer- 2 issues (1997)
ShipCost Data Base (1998)
WebDNA on RHEL4 (2007)
Which GUI HTML editors work with WC ? (1997)
Re[3]: 2nd WebCatalog2 Feature Request (1996)
Database Structuring (again) (2003)
Talk List Archive Down? (2004)
WebCat2 - many [carts] on one template page? (1997)
Smart caching problems with 2.1b3? (1997)
Weird [date] and [time] problems. (2003)