Re: [WebDNA] HTML/OS vs. WebDNA ?
This WebDNA talk-list message is from 2008
It keeps the original formatting.
numero = 100903
interpreted = N
texte = I have never used HTML/OS that's why I was asking if anyone else has, so I could get some first-hand feedback. Some of the descriptions on the Aestiva website sound a lot like WebDNA and it has some interesting features that are rather appealing -- if they actually work: For one, you apparently do not have to pass variable name=value pairs from page to page because once they are created they remain available on all pages. In other words, the server 'maintains the state of the visitor' somehow. Don't ask me how, but that's what is claimed. I would like to know how they do this but I haven't found anything yet in the online info that explains it and I haven't experimented with it to figure it out myself yet. Another feature I found to be rather attractive is that once it is installed, it is managed by a control panel which provides all the tools needed to create and administer the databases, plus the tools for installing seamless upgrades. It looks kind of like a cPanel for HTML/OS, and I think something similar for WebDNA would make it easier for beginners to use sometimes. But the thing that most interested me is that it is apparently possible to develop self-contained HTML/OS apps that you can sell to your customers, and they will install on practically any server, even if all the customer has is a cheap $% per month hosting account on a shared server! I'm pretty sure this is because it is just an 'old-fashioned cgi' that runs in practically any cgi-bin folder on any server. This probably means it will not be the fastest solution for a heavily visited website, but then again ... If I develop something like a simple home budget tool in HTML/OS I should never have a problem with its installation on whatever server the customer happens to be using. Imagine developing and selling 100,000 copies of a $5 or program that "just works" on all servers! I'm not sure if it makes sense for WebDNA to move in the direction of offering similar capabilities to the ones I've mentioned here. Even if this is the way Chris and Donoval choose to go, my guess is that such new features will have to wait until some of the existing bugs and other long-standing issues are corrected first. But it is rather interesting to consider some new possibilities for WebDNA's long-term future! :) Sincerely, Ken Grome
Associated Messages, from the most recent to the oldest:
I have never used HTML/OS that's why I was asking if anyone else has, so I could get some first-hand feedback. Some of the descriptions on the Aestiva website sound a lot like WebDNA and it has some interesting features that are rather appealing -- if they actually work: For one, you apparently do not have to pass variable name=value pairs from page to page because once they are created they remain available on all pages. In other words, the server 'maintains the state of the visitor' somehow. Don't ask me how, but that's what is claimed. I would like to know how they do this but I haven't found anything yet in the online info that explains it and I haven't experimented with it to figure it out myself yet. Another feature I found to be rather attractive is that once it is installed, it is managed by a control panel which provides all the tools needed to create and administer the databases, plus the tools for installing seamless upgrades. It looks kind of like a cPanel for HTML/OS, and I think something similar for WebDNA would make it easier for beginners to use sometimes. But the thing that most interested me is that it is apparently possible to develop self-contained HTML/OS apps that you can sell to your customers, and they will install on practically any server, even if all the customer has is a cheap $% per month hosting account on a shared server! I'm pretty sure this is because it is just an 'old-fashioned cgi' that runs in practically any cgi-bin folder on any server. This probably means it will not be the fastest solution for a heavily visited website, but then again ... If I develop something like a simple home budget tool in HTML/OS I should never have a problem with its installation on whatever server the customer happens to be using. Imagine developing and selling 100,000 copies of a $5 or program that "just works" on all servers! I'm not sure if it makes sense for WebDNA to move in the direction of offering similar capabilities to the ones I've mentioned here. Even if this is the way Chris and Donoval choose to go, my guess is that such new features will have to wait until some of the existing bugs and other long-standing issues are corrected first. But it is rather interesting to consider some new possibilities for WebDNA's long-term future! :) Sincerely, Ken Grome
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:
Sherlock plug-in? (1999)
# fields limited? (1997)
SSL (1998)
Almost a there but..bye bye NetCloak (1997)
WebCat .pdf file is still messed up... (2000)
Document contains no data... (1999)
Alcatraz must have been nicer than this... (2000)
Multiple Sendmail Tags on One Page (2008)
still having shipCost.db Problem (1997)
Sku numbers (1997)
Appending current [date] to a database (1997)
[format xs] freeze (1997)
Talk List Suggestions (1997)
same product in cart (1997)
Merging databases (1997)
OSX 10.2.6/iTools 7.0/WebDNA 5.0 installation (2003)
Online reference (1997)
Multiple fields on 1 input (1997)
possible, WebCat2.0 and checkboxes-restated (1997)
accountnum using [listwords] (2001)