thanks for your quick answer. I will try the links and
post my results within this thread.
Maybe I have a wrong perspective. Could you please tell
me what is the prefered way to deal with Autobahn from the server side?
Shoud it run standalone as a daemon?
For production use, either
1) run Autobahn standalone (it's quite capable .. we've tested up to 180k concurrently active WebSocket connections with Autobahn running on a 2-core VM with 4GB Ram - and you don't have a 2nd source of security issues)
2) run it behind a _capable_ and WS-aware Web server: nginx
3) run it behind a L4 loadbalancer/firewall: OpenBSD/relayd/pf
4) run it behind a WS-aware L7 loadbalancer/proxy: haproxy
In general, I'd go with 1) or 2) unless you have specific needs and
know what you are doing ..
Apache is getting ooold;)
Am 14.10.2013 16:33, schrieb Marco Schrank:
You received this message because you are subscribed to the Google
Groups "Autobahn" group.
To unsubscribe from this group and stop receiving emails from it, send
an email to autobahnws+...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.