Understand....and do know that when services/sites are not engineered correctly this will happen.
Here is how Flickr have architected their service.
A couple of suggestions:
- take a look to nginx, it's really fast and for a fast switch there is
need for a fast data backend (it serves data)
- dosen't use php (i love php, but it is slow ... a lot slow even using
apc, eaccelerator or similar!)
Memcached (or similar like sharedance) would be really useful to serve
pre generated XML.
It would be really nice if the WUI (Web UI) would be written using Mono
or Python
these are just my two cents :)
_______________________________________________
Freeswitch-users mailing list
Freeswitch-users@lists.freeswitch.org
http://lists.freeswitch.org/mailman/listinfo/freeswitch-users
UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users
http://www.freeswitch.org