Re: [WebDNA] WebDNA future
This WebDNA talk-list message is from 2010
It keeps the original formatting.
numero = 104407
interpreted = N
texte = christophe.billiottet@webdna.us wrote: > First of all, we do not remove anything, on the contrary: we fill out the documentation; compare http://www.webdna.us/page.dna?numero=84 with the old http://docs.webdna.us/ArraySetContext.html for instance. > > Unfortunately, "anyone best interest" (as Ken said) is not attracting many new customers. We put WebDNA on the right track and make everything right. Some will offer resistance to changes and just argue about anything, but we want to move forward and give WebDNA the commercial success it deserves, which would translate into an easy to install, easy to use, solid, fast and stable product. > > We focuse on the core engine, while the external applications like StoreBuilder and CMS will become external offers. > > An engine that could run on most platforms with most webservers implies a fastCGI architecture (remember 6.2 only runs with apache 2.2 which has been a serious limitation for years, without any benefit). "fastCGI" implies no more sandboxes, which will disappear. The URL command will be deprecated as it can jeopardise security and is not used anymore. The licensing system has been entirely rewritten, simplified, is cross-platform and will allow one WebDNA copy to run on a single website, for a cheap price. We are working on many more modifications at this time. The WebDNA version is already running but needs more work. > > About the question "will you still support the module version of WebDNA", answer is "yes". > > In the future, i was thinking in parallel processing WebDNA servers and high resilience WebDNA database servers using clusters with fully scalable solutions. But this is another story... :-) > > - chris--------------------------------------------------------- Thanks Chris,.. I think more clarifications on your vision would be appreciated publicly for us as small business men etc.. to know where we are going with WebDNA: Can you clarify what will be included in both app types and what won't? If you need to keep it a secret, then that is fine... but it doesn't hurt to ask, right!? Will the module app type remain as-is? - globals directory? - xml contexts? - Sandboxes? - commands? - ide, sitebuilder etc?? - admin interface Will the fastCGI app have: - Globals directory? - XML? - admin interface? Thanks, 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: > First of all, we do not remove anything, on the contrary: we fill out the documentation; compare http://www.webdna.us/page.dna?numero=84 with the old http://docs.webdna.us/ArraySetContext.html for instance. > > Unfortunately, "anyone best interest" (as Ken said) is not attracting many new customers. We put WebDNA on the right track and make everything right. Some will offer resistance to changes and just argue about anything, but we want to move forward and give WebDNA the commercial success it deserves, which would translate into an easy to install, easy to use, solid, fast and stable product. > > We focuse on the core engine, while the external applications like StoreBuilder and CMS will become external offers. > > An engine that could run on most platforms with most webservers implies a fastCGI architecture (remember 6.2 only runs with apache 2.2 which has been a serious limitation for years, without any benefit). "fastCGI" implies no more sandboxes, which will disappear. The URL command will be deprecated as it can jeopardise security and is not used anymore. The licensing system has been entirely rewritten, simplified, is cross-platform and will allow one WebDNA copy to run on a single website, for a cheap price. We are working on many more modifications at this time. The WebDNA version is already running but needs more work. > > About the question "will you still support the module version of WebDNA", answer is "yes". > > In the future, i was thinking in parallel processing WebDNA servers and high resilience WebDNA database servers using clusters with fully scalable solutions. But this is another story... :-) > > - chris--------------------------------------------------------- Thanks Chris,.. I think more clarifications on your vision would be appreciated publicly for us as small business men etc.. to know where we are going with WebDNA: Can you clarify what will be included in both app types and what won't? If you need to keep it a secret, then that is fine... but it doesn't hurt to ask, right!? Will the module app type remain as-is? - globals directory? - xml contexts? - Sandboxes? - commands? - ide, sitebuilder etc?? - admin interface Will the fastCGI app have: - Globals directory? - XML? - admin interface? Thanks, 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:
Need relative path explanation (1997)
[WriteFile] problems (1997)
JavaScript form question (2001)
Quickie question on the email templates (1997)
Textarea Breaks (2000)
Adding Multiple Items to Shopping Cart from a Results page (1997)
Ampersand in XHTML Code - Not Valid (2005)
Setting up shop (1997)
Showing specific [cart] contents (1998)
RE: [WebDNA] ONLY the FIRST continuous run of numeric chars? (2008)
Form Submition (2003)
WebCat2 several catalogs? (1997)
Help! Strange happenings... (1997)
[WebDNA] v7 help (2012)
multi-paragraph fields (1997)
Hosting (2000)
Re1000001: Setting up shop (1997)
ImageMap (1997)
lookup and two records? (1997)
Calendar Program (2004)