2012

We're using version 7 since a few weeks =and I really like the product.

I also like the many times discussed fcgi solution.
We had performance problems in the past, heavy load on a few vhosts brought= us waiting times up to 5 seconds per page, for all vhosts, not just the on=es with heavy load, because with v6 a single webdna process is responsible =for all vhosts.

Having the ability to split the load on many separate webdna processes will= solve this problem.


I moved our CMS to v7, took me two days of programming, but only because we= used global databases to store informations about which CMS modules to ser=ve for each client, versions installed and a copy protection system of all =our CMS clients. We solved this problem with a databases on an own vhost, a=ll our CMS systems are exchanging informations with this global database us=ing CURL commands.
So there's no more need for global databases in our case.

All the other functions worked just perfect as they did before. My concerns= about incompatibility were absolutely unnecessary.
(excluding the [thisurl]-tag discussed in another thread in this list)

And it's even possible to serve v6 and v7 sites on the same server, jus=t make sure you use different suffixes for v6 and v7.
Because we wanted to have .tpl for v6 and .dna for v7 and I had to make som=e changes to the v6 administration.


During the next weeks we'll move a few more sites with heavy load to v7=.



At this point I'd like to put a big THANK YOU into this list, thank you= Chris, thank you community!
This product and its further development saves our a... and it's worth =a lot more than it costs ;-)


Thierry---------------------------------------------------------
This message is sent to you because you are subscribed to
the mailing list <talk@webdna.us&g=t;.
To unsubscribe, E-mail to: <talk=-leave@webdna.us>
archives: http://mail.webdna.us/list/talk@webdna.us
Bug Reporting: support@webdna.us