Hello

Until the last years, I did run 4D with Active4D and a 4D Webserver license  
compiled on a normal 4D application on OS X.
Since a view month it works now all with Active4D 4.5 and 4Dv11 and OS X 10.6.
Since one year the traffic on the webserv is going up and up, and I think about 
to run it in a different way.

Current setting:
I have one Mac for the Editors.
And one for the normal web-users.
And about 100'000 images, which are syncronized each 3 Minutes with Synchronize 
Pro. And the same with the over 100'000 articles from one to the other 4D 
Database with http-requests and Record-to-Blob methods.
Now I want to change philosophy, and use a 4D11 Server.

What is best?

New Setting Version 1:
Mac1: 4D11 Server + Webserver -> for Editors (not much performance needed, but 
it should not crash!)
Mac2: 4D11 Client + Webserver -> for Web-User (hight performance, and can 
crash...)

New Setting Version 2:
Mac1: 4D11 Server
Mac2: 4D11 Client + Webserver -> for Editors 
Mac3: 4D11 Client + Webserver -> for Web-User

New Setting Version 3:
???
???


And is it an Idea to have the images only on one of the Macs, and share this 
volume to the others. (Most images are resized for the web-users and saved in a 
cash of each webserver, so it it should not be a performance problem when share 
a Volume to all macs.

And all the scripts have to be an all Servers? (more then 1'000 a4d-scripts). 
But this is no problem, because I don't have to change them very often.

Is there a stability problem when using 4D Server, or is it more stable?
Is there a big performance when using 4D Server and the webserver on clients?

Sorry about my questions, but after a lot of years developing without 4D 
Server, this is a total new thing for me.

And here is the Website:
http://www.jungfrauzeitung.ch/

Regards, Oliver
_______________________________________________
Active4D-dev mailing list
[email protected]
http://mailman.aparajitaworld.com/mailman/listinfo/active4d-dev
Archives: http://mailman.aparajitaworld.com/archive/active4d-dev/

Reply via email to