[WebDNA] WordPress plugin

This WebDNA talk-list message is from

2020


It keeps the original formatting.
numero = 115149
interpreted = N
texte = 2778 WordPress uses MySQL, or whatever database it=E2=80=99s configured for. = Why couldn=E2=80=99t WebDNA be packaged as a plugin for WordPress which = would replace the database connection with its own fast, RAM system? Even if you completely ignored it=E2=80=99s fantastic scripting = language, simply configuring a FastGCI WordPress plugin to shuffle data = requests between the CMS and RAM based data, it would dramatically speed = up WordPress. Future versions might expand to include a way to edit content using the = WebDNA interpreter, but that can be an entirely separate project. Currently, the entire world seems hypnotized into believing that there = needs to be a separate database software system and that=E2=80=99s = antiquated nonsense. There=E2=80=99s certainly needs to be structured = data, but requiring it flow over a serialized, disk-centric serial model = that only made sense with a mainframe is hopeless. --------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list talk@webdna.us To unsubscribe, E-mail to: talk-leave@webdna.us archives: http://www.webdna.us/page.dna?numero=3D55 Bug Reporting: support@webdna.us . Associated Messages, from the most recent to the oldest:

    
  1. Re: [WebDNA] WordPress plugin (Palle Bo Nielsen 2020)
  2. Re: [WebDNA] WordPress plugin (Michael Davis 2020)
  3. Re: [WebDNA] WordPress plugin (Stuart Tremain 2020)
  4. Re: [WebDNA] WordPress plugin (christophe.billiottet@webdna.us 2020)
  5. Re: [WebDNA] WordPress plugin (Stuart Tremain 2020)
  6. [WebDNA] WordPress plugin (Patrick McCormick 2020)
2778 WordPress uses MySQL, or whatever database it=E2=80=99s configured for. = Why couldn=E2=80=99t WebDNA be packaged as a plugin for WordPress which = would replace the database connection with its own fast, RAM system? Even if you completely ignored it=E2=80=99s fantastic scripting = language, simply configuring a FastGCI WordPress plugin to shuffle data = requests between the CMS and RAM based data, it would dramatically speed = up WordPress. Future versions might expand to include a way to edit content using the = WebDNA interpreter, but that can be an entirely separate project. Currently, the entire world seems hypnotized into believing that there = needs to be a separate database software system and that=E2=80=99s = antiquated nonsense. There=E2=80=99s certainly needs to be structured = data, but requiring it flow over a serialized, disk-centric serial model = that only made sense with a mainframe is hopeless. --------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list talk@webdna.us To unsubscribe, E-mail to: talk-leave@webdna.us archives: http://www.webdna.us/page.dna?numero=3D55 Bug Reporting: support@webdna.us . Patrick McCormick

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:

File Uploads... (1997) Snake Bites (1997) Re(6): Small Bug: ErrorLog.txt/[FORMVARIABLES]/[ORDERFILE] (1998) [WebDNA] WebDNA glitch, no response required ... (2009) Multiple Ad databases? (1997) Follow-Up to: Removing [showif] makes a big difference in speed (1997) Searching Groups for multiple matches (1998) Help SM: Duplicate cart #'s - still! (2003) Running _every_ page through WebCat ? (1997) Faxing orders in place of email (1997) Color options for items (1999) database size? (1997) Bug or syntax error on my part? (1997) [append] vs. [appendfile] delta + question? (1997) Summing fields (1997) Speaking of Rediret (2004) input problem (1999) Way Off Topic (2003) OFF-TOPIC: Stop reloading SRC page from cache ... (2003) OT: CSS and Positioning (2001)