Re: [WebDNA] WordPress plugin

This WebDNA talk-list message is from

2020

It keeps the original formatting. numero = 115152
interpreted = N
texte = 2781--Apple-Mail=_62CC52F0-7098-4696-AAB2-ADFE4CF54FDBContent-Transfer-Encoding: quoted-printableContent-Type: text/plain;charset=utf-8FANTASTIC !!!Kind regardsStuart TremainPharoah Lane SoftwareAUSTRALIAwebdna@plsoftware.com.au> On 28 Jul 2020, at 15:57, talk@webdna.us wrote:>=20> Hello everyone,>=20> We are currently working on such a solution. Multiple copies of WebDNA =on several servers would either be able to share a single database on a =single server, and/or to locally replicate a database from a server A to =a server B.>=20> This is a major update that we are working on and it might be our =WebDNA 9.0.>=20> Stay tuned :-)>=20> - chris>=20>=20>=20>=20>=20>=20>> On Jul 28, 2020, at 01:36, talk@webdna.us wrote:>>=20>> The big advantage to having a standalone db system is that you can =have a multi server (not website), one database system that you see on =busy websites, unfortunately WebDNA does not support this model =E2=80=98o=ut of the box=E2=80=99. I have considered building a system to support =this but have not had the time and have stuck with WebDNA & MySQL, and =consequently such with WebDNA 8.2 server edition, would love to see =MySQL or MariaDB or PostgreSQL integrated into the new WebDNA editions.>>=20>> I think that the requirements to convert MySQL queries to WebDNA is =probably not too hard on first glance but there are things that MySQL =natively can do that WebDNA would need to be programmed to do.>>=20>> In developing a WebDNA dB to replace MySQL for Wordpress you would =have to be able to replicate all the aspects of MySQL and I think for =the market that you are considering ie Wordpress/MySQL, would just =ignore it.=20>>=20>> As much as I love WebDNA it does have it limitations when it comes to =large data.>>=20>> The most common website config is MySQL/PHP on Linux servers (LAMP), =I would love to see a common LAW solution (Linux And WebDNA).>>=20>> The biggest thing that I would like to see is a multi server/single =db solution for WebDNA.>>=20>>=20>> Kind regards>>=20>> Stuart Tremain>> Pharoah Lane Software>> AUSTRALIA>> webdna@plsoftware.com.au>>=20>>=20>>=20>>=20>>=20>>=20>>=20>>> On 28 Jul 2020, at 08:08, talk@webdna.us wrote:>>>=20>>> 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?>>>=20>>> 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.>>>=20>>> Future versions might expand to include a way to edit content using =the WebDNA interpreter, but that can be an entirely separate project.>>>=20>>> 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.>>>=20>>>=20>>> --------------------------------------------------------->>> 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>>=20>> --------------------------------------------------------- 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>=20> ---------------------------------------------------------> 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--Apple-Mail=_62CC52F0-7098-4696-AAB2-ADFE4CF54FDBContent-Transfer-Encoding: quoted-printableContent-Type: text/html;charset=utf-8FANTASTIC !!!

Kind regards

Stuart Tremain

Pharoah Lane Software

AUSTRALIA

webdna@plsoftware.com.au

On 28 Jul 2020, at 15:57, talk@webdna.us wrote:

Hello =everyone,

We are currently working on such =a solution. Multiple copies of WebDNA on several servers would either be =able to share a single database on a single server, and/or to locally =replicate a database from a server A to a server B.

This is a major update that we are working on and it might be =our WebDNA 9.0.

Stay tuned :-)

- chris

On Jul 28, 2020, at =01:36, talk@webdna.us =wrote:

The big advantage to having a =standalone db system is that you can have a multi server (not website), =one database system that you see on busy websites, unfortunately WebDNA =does not support this model =E2=80=98out of the box=E2=80=99. I have =considered building a system to support this but have not had the time =and have stuck with WebDNA & MySQL, and consequently such with =WebDNA 8.2 server edition, would love to see MySQL or MariaDB or =PostgreSQL integrated into the new WebDNA editions.

I think that the requirements to convert MySQL queries to =WebDNA is probably not too hard on first glance but there are things =that MySQL natively can do that WebDNA would need to be programmed to =do.

In developing a WebDNA dB to =replace MySQL for Wordpress you would have to be able to replicate all =the aspects of MySQL and I think for the market that you are considering =ie Wordpress/MySQL, would just ignore it.

As= much as I love WebDNA it does have it limitations when it comes to =large data.

The most common website config =is MySQL/PHP on Linux servers (LAMP), I would love to see a common LAW =solution (Linux And WebDNA).

The biggest =thing that I would like to see is a multi server/single db solution for =WebDNA.

Kind regards

Stuart Tremain
Pharoah Lane =Software
AUSTRALIA
webdna@plsoftware.com.au

On 28 Jul 2020, at =08:08, talk@webdna.us wrote:

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

--------------------------------------------------------- =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

---------------------------------------------------------
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

=---------------------------------------------------------This message is sent to you because you are subscribed tothe mailing list talk@webdna.usTo unsubscribe, E-mail to: talk-leave@webdna.usarchives: http://www.webdna.us/page.dna?numero=3D55Bug Reporting: support@webdna.us--Apple-Mail=_62CC52F0-7098-4696-AAB2-ADFE4CF54FDB--. Associated Messages, from the most recent to the oldest:

Re: [WebDNA] WordPress plugin (Palle Bo Nielsen 2020)
Re: [WebDNA] WordPress plugin (Michael Davis 2020)
Re: [WebDNA] WordPress plugin (Stuart Tremain 2020)
Re: [WebDNA] WordPress plugin (christophe.billiottet@webdna.us 2020)
Re: [WebDNA] WordPress plugin (Stuart Tremain 2020)
[WebDNA] WordPress plugin (Patrick McCormick 2020)

2781--Apple-Mail=_62CC52F0-7098-4696-AAB2-ADFE4CF54FDBContent-Transfer-Encoding: quoted-printableContent-Type: text/plain;charset=utf-8FANTASTIC !!!Kind regardsStuart TremainPharoah Lane SoftwareAUSTRALIAwebdna@plsoftware.com.au> On 28 Jul 2020, at 15:57, talk@webdna.us wrote:>=20> Hello everyone,>=20> We are currently working on such a solution. Multiple copies of WebDNA =on several servers would either be able to share a single database on a =single server, and/or to locally replicate a database from a server A to =a server B.>=20> This is a major update that we are working on and it might be our =WebDNA 9.0.>=20> Stay tuned :-)>=20> - chris>=20>=20>=20>=20>=20>=20>> On Jul 28, 2020, at 01:36, talk@webdna.us wrote:>>=20>> The big advantage to having a standalone db system is that you can =have a multi server (not website), one database system that you see on =busy websites, unfortunately WebDNA does not support this model =E2=80=98o=ut of the box=E2=80=99. I have considered building a system to support =this but have not had the time and have stuck with WebDNA & MySQL, and =consequently such with WebDNA 8.2 server edition, would love to see =MySQL or MariaDB or PostgreSQL integrated into the new WebDNA editions.>>=20>> I think that the requirements to convert MySQL queries to WebDNA is =probably not too hard on first glance but there are things that MySQL =natively can do that WebDNA would need to be programmed to do.>>=20>> In developing a WebDNA dB to replace MySQL for Wordpress you would =have to be able to replicate all the aspects of MySQL and I think for =the market that you are considering ie Wordpress/MySQL, would just =ignore it.=20>>=20>> As much as I love WebDNA it does have it limitations when it comes to =large data.>>=20>> The most common website config is MySQL/PHP on Linux servers (LAMP), =I would love to see a common LAW solution (Linux And WebDNA).>>=20>> The biggest thing that I would like to see is a multi server/single =db solution for WebDNA.>>=20>>=20>> Kind regards>>=20>> Stuart Tremain>> Pharoah Lane Software>> AUSTRALIA>> webdna@plsoftware.com.au>>=20>>=20>>=20>>=20>>=20>>=20>>=20>>> On 28 Jul 2020, at 08:08, talk@webdna.us wrote:>>>=20>>> 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?>>>=20>>> 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.>>>=20>>> Future versions might expand to include a way to edit content using =the WebDNA interpreter, but that can be an entirely separate project.>>>=20>>> 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.>>>=20>>>=20>>> --------------------------------------------------------->>> 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>>=20>> --------------------------------------------------------- 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>=20> ---------------------------------------------------------> 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--Apple-Mail=_62CC52F0-7098-4696-AAB2-ADFE4CF54FDBContent-Transfer-Encoding: quoted-printableContent-Type: text/html;charset=utf-8FANTASTIC !!!