Re: [WebDNA] WebDNA future
This WebDNA talk-list message is from 2010
It keeps the original formatting.
numero = 104419
interpreted = N
texte = christophe.billiottet@webdna.us wrote: > You are a shareholder Donovan. Feel free to ask privately. WebDNA is not obsessed with secrecy, but some information are not for public release yet. > > - chris Obviously, my intention was to try and spark some *constructive* 3rd party conversation on some of the ideas (new app type, website, and documentation etc..) that have been made public... as I think you would admit that you and I have come to beating the poor dead horse with many of our views. ;-) Since these ideas have indeed been made public, I think it's fair to ask questions and/or talk about them a bit. Understand, I'm not trying to be a complainer, but rather, I am trying to help by first clarifying some of the details and perhaps pointing out some concerns, and then perhaps sparking some new input about those ideas. Afterall, I see our original intention of this product to be developer owned... so in that spirit.... First, the FastCGI is a great *option* IMO. I think everyone will agree, once they think about it, that it allows for a perhaps simpler alternative in virtual hosting environments (one, because it can run as the same user/group as the virtual environment, which sometimes is different than the webserver's user/group enviro), and offers some isolation benefits (.."what happens in my home doesn't affect yours" sort of thing). Also, chances are that more big name virtual hosting environments will allow it, though there will still be many that won't. In short, along with the benefits you pointed out, it opens up a wider and simpler market that now better includes WebSite owners who rent a virtual host and people who want to keep their virtual hosts as separate as possible. I personally applaud the effort in that direction (as I did when I was involved). However, there are reasons to keep the plug-in (module) version up-to-date..., which is still unclear by everyone except you and Jaz. And though I may actually have a clue on some of the answers that I'm asking, ;-) I thought it best to ask if you could reveal some of that intention so that you can get, not just my feedback, but feedback from the other experienced scriptors and admins here. Regarding some of the comments, here is some of the responses that I have... With sandboxes, an admin has the ability to limit how a user can interact with the rest of the server, particularly with DOS,SHELL,Applescript, file paths et al. Has this sort of thing been addressed with the fastCGI app that will most likely run in virtual host situation? I don't know of anyone that will want to install an app in a shared host enviro that will have the ability to fish around the entire server. Knowing Jaz though, I'm guessing he has already thought of this and addressed this.?? It seems like the only solution there is relative paths only, as not all domains will have different user and groups. Contrary to what was said, there *are* many who still use commands.. mostly because there are many who run SiteBuilder stores (which use commands). Now, I personally think SiteBuilder is outdated and needs an upgrade, particularly replacing the commands with contexts... However, the fact remains that it is functional, people use it, people make money with it, and yes, if done right, it can be secure. I know people use commands because I have worked on some of those sites. If commands are to be taken out of all the versions of WebDNA, those sites are dead in the water without reworks and the SiteBuilder product becomes a dead product without a rework. (Fine with me if that is the case, but significant none the less to quite a few, and something people may want a heads up on) 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. Those are some initial concerns... and again... yes, this may be a bit of an uncomfortable "tactic".. but I'm just trying to help see a successful WebDNA future. I look forward to trying out the fastCGI app.! Donovan -- Donovan Brooke Euca Design Center [Practical-Ethical-Efficient] www.euca.us egg.bz artglass-forum.com
Associated Messages, from the most recent to the oldest:
christophe.billiottet@webdna.us wrote: > You are a shareholder Donovan. Feel free to ask privately. WebDNA is not obsessed with secrecy, but some information are not for public release yet. > > - chris Obviously, my intention was to try and spark some *constructive* 3rd party conversation on some of the ideas (new app type, website, and documentation etc..) that have been made public... as I think you would admit that you and I have come to beating the poor dead horse with many of our views. ;-) Since these ideas have indeed been made public, I think it's fair to ask questions and/or talk about them a bit. Understand, I'm not trying to be a complainer, but rather, I am trying to help by first clarifying some of the details and perhaps pointing out some concerns, and then perhaps sparking some new input about those ideas. Afterall, I see our original intention of this product to be developer owned... so in that spirit.... First, the FastCGI is a great *option* IMO. I think everyone will agree, once they think about it, that it allows for a perhaps simpler alternative in virtual hosting environments (one, because it can run as the same user/group as the virtual environment, which sometimes is different than the webserver's user/group enviro), and offers some isolation benefits (.."what happens in my home doesn't affect yours" sort of thing). Also, chances are that more big name virtual hosting environments will allow it, though there will still be many that won't. In short, along with the benefits you pointed out, it opens up a wider and simpler market that now better includes WebSite owners who rent a virtual host and people who want to keep their virtual hosts as separate as possible. I personally applaud the effort in that direction (as I did when I was involved). However, there are reasons to keep the plug-in (module) version up-to-date..., which is still unclear by everyone except you and Jaz. And though I may actually have a clue on some of the answers that I'm asking, ;-) I thought it best to ask if you could reveal some of that intention so that you can get, not just my feedback, but feedback from the other experienced scriptors and admins here. Regarding some of the comments, here is some of the responses that I have... With sandboxes, an admin has the ability to limit how a user can interact with the rest of the server, particularly with DOS,SHELL,Applescript, file paths et al. Has this sort of thing been addressed with the fastCGI app that will most likely run in virtual host situation? I don't know of anyone that will want to install an app in a shared host enviro that will have the ability to fish around the entire server. Knowing Jaz though, I'm guessing he has already thought of this and addressed this.?? It seems like the only solution there is relative paths only, as not all domains will have different user and groups. Contrary to what was said, there *are* many who still use commands.. mostly because there are many who run SiteBuilder stores (which use commands). Now, I personally think SiteBuilder is outdated and needs an upgrade, particularly replacing the commands with contexts... However, the fact remains that it is functional, people use it, people make money with it, and yes, if done right, it can be secure. I know people use commands because I have worked on some of those sites. If commands are to be taken out of all the versions of WebDNA, those sites are dead in the water without reworks and the SiteBuilder product becomes a dead product without a rework. (Fine with me if that is the case, but significant none the less to quite a few, and something people may want a heads up on) 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. Those are some initial concerns... and again... yes, this may be a bit of an uncomfortable "tactic".. but I'm just trying to help see a successful WebDNA future. I look forward to trying out the fastCGI app.! Donovan -- Donovan Brooke Euca Design Center [Practical-Ethical-Efficient] www.euca.us egg.bz artglass-forum.com
Donovan Brooke
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:
url value (2002)
Virtual hosting and webcatNT (1997)
WebCat2b13MacPlugIn - [showif][search][/showif] (1997)
Wrapping text (1998)
[WebDNA] Migration from 6.2 to 7. Problems with writing to DB's (2012)
Mac OS X ODBC (2002)
Security Issues and WebCommerce Solution (1997)
Interfacing WebMerchant to www.fedex.com (1997)
Encyption mail was Suggestions for Topics ... (1998)
HELP WITH DATES (1997)
WebCatalog Q & A pages (1997)
Here's how to kill a Butler Database. (1997)
Parsing webdna variable to javascript (2005)
Silly Question (1997)
headers (2004)
Getting URL's entered manually (1997)
So, does anyone have developer editon running on Win XP (2006)
Looking up two prices in database? (1997)
Help formatting search results w/ table (1997)
ShowIf inside formulas (1997)