RE: [WebDNA] a major shift in strategy?
This WebDNA talk-list message is from 2008
It keeps the original formatting.
numero = 101101
interpreted = N
texte = Hey braddah Ken, you like me buss out da pidgin huh! > New concept! Good 'outside the box' thinking. Totally > re-positions the software in the marketplace by targeting > MySQL. Interesting ... but with (presumably) limited funds > for development I think it's not doable in this decade. You are probably right though I have some faith that the architecture can migrate towards this type of system. WebDNA is essentially a database server already. It would be cool to use some type of exec function to call the db server and get back the results in a format that many developers already use like JSON or XML. So...query the service locally or even remotely then manipulate the returned object to display the results. Webdna just has to return the results wrapped in the plain text package of choice (personally I like XML). Nearly all developers today that work with web services would be able to get up and running in no time. Here are some interesting database as a service options: http://aws.amazon.com/simpledb/ from Amazon, http://hadoop.apache.org/hbase/, http://www.hypertable.org/, and http://labs.google.com/papers/bigtable.html soon to be released by Google. So I guess this is like accessing your database in a web services like paradigm versus a SQL based paradigm. I actually built something a little like this with webdna. If you go to Jack Johnson's All at Once site - http://www.jackjohnsonmusic.com/allatonce/ - you'll see a system where you can make personal commitments. It's a really simple interface but the implementation is interesting. The site is PHP based and when the site needs to store, retrieve, or edit commitments and commitment impacts, it makes a call to a webdna server which then returns the results in JSON format. The webdna server manages all of the data needs and has a bunch of logic to calculate complex impact formulas. Works like a charm :) You should all go sign up and make commitments...Jack Johnson is passing out free songs to folks that do. By the way, we did something similar with http://sproutbuilder.com/. We built a system that lets you create extremely sophisticated flash widgets/mash ups without writing a single line of code. Designers then can do what they want without the bottleneck of a Flash developer. Same concept here. Programmer get things done without the bottleneck of a database admin. Oh, we wrote the prototype for Sprout in a couple of months in webdna! Once the prototype proved the model, the system as it is hosted now was developed in PHP/mysql. We also did the same for fundraising with http://ChipIn.com where folks don't need to focus on developing the viral tools for raising money or work with a developer to track fundraising status. I know this all sounds crazy but I sure would love to see webdna succeed so am just tossing out some ideas. Consider me part of the solution...whatever collectively that turns out to be.
Associated Messages, from the most recent to the oldest:
Hey braddah Ken, you like me buss out da pidgin huh! > New concept! Good 'outside the box' thinking. Totally > re-positions the software in the marketplace by targeting > MySQL. Interesting ... but with (presumably) limited funds > for development I think it's not doable in this decade. You are probably right though I have some faith that the architecture can migrate towards this type of system. WebDNA is essentially a database server already. It would be cool to use some type of exec function to call the db server and get back the results in a format that many developers already use like JSON or XML. So...query the service locally or even remotely then manipulate the returned object to display the results. Webdna just has to return the results wrapped in the plain text package of choice (personally I like XML). Nearly all developers today that work with web services would be able to get up and running in no time. Here are some interesting database as a service options: http://aws.amazon.com/simpledb/ from Amazon, http://hadoop.apache.org/hbase/, http://www.hypertable.org/, and http://labs.google.com/papers/bigtable.html soon to be released by Google. So I guess this is like accessing your database in a web services like paradigm versus a SQL based paradigm. I actually built something a little like this with webdna. If you go to Jack Johnson's All at Once site - http://www.jackjohnsonmusic.com/allatonce/ - you'll see a system where you can make personal commitments. It's a really simple interface but the implementation is interesting. The site is PHP based and when the site needs to store, retrieve, or edit commitments and commitment impacts, it makes a call to a webdna server which then returns the results in JSON format. The webdna server manages all of the data needs and has a bunch of logic to calculate complex impact formulas. Works like a charm :) You should all go sign up and make commitments...Jack Johnson is passing out free songs to folks that do. By the way, we did something similar with http://sproutbuilder.com/. We built a system that lets you create extremely sophisticated flash widgets/mash ups without writing a single line of code. Designers then can do what they want without the bottleneck of a Flash developer. Same concept here. Programmer get things done without the bottleneck of a database admin. Oh, we wrote the prototype for Sprout in a couple of months in webdna! Once the prototype proved the model, the system as it is hosted now was developed in PHP/mysql. We also did the same for fundraising with http://ChipIn.com where folks don't need to focus on developing the viral tools for raising money or work with a developer to track fundraising status. I know this all sounds crazy but I sure would love to see webdna succeed so am just tossing out some ideas. Consider me part of the solution...whatever collectively that turns out to be.
"Olin Lagon"
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:
date (1998)
Help name our technology! (1997)
billing system (2003)
Affiliate Marketing Question #2 (1998)
Webcatalog quitting (1997)
Credit card processing options. . . (1997)
OS Limitations (1998)
sharing cookie recepies (1998)
[BoldWords] WebCat.acgib15Mac (1997)
$quit / Command=Quit (2002)
Webstar 1.3.1 PPC (1997)
DB Commit (2000)
DataBaseHelper Flawed (1997)
[ListFiles] & [loop] (1998)
PIXO support (1997)
tiny Linux issue (1999)
Problem with ShoppingCart.tpl refresh (2000)
Problems with webcat 2.01 for NT (1997)
Version f1 status (1997)
Danger of [newcart] (1999)