Robert Pankowecki
Robert Pankowecki
Try to keep the API compatible with what Aaron describes here: http://www.youtube.com/watch?v=kufXhNkm5WU . Maybe just change the included module to `M2R::Live` ? Maybe that should be a different gem, but...
Related to #42
http://polycrystal.org/2012/04/15/asynchronous_responses_in_rack.html
- http://blog.phusion.nl/2013/01/23/the-new-rack-socket-hijacking-api/ - http://rack.rubyforge.org/doc/SPEC.html - http://ngauthier.com/2013/03/websockets-in-rails-4.html
I found a workaround in: ``` git clone https://github.com/devspace-cloud/component-chart helm install -f helm-only-app.yml -n my-namespace my-component ./component-chart ```
Maybe the problem comes from `CONT` signal: ``` Down. If the service is running, send it a TERM signal, and then a CONT signal. If ./run exits, start ./finish if...
Let me share a few thoughts about our issues that we recently discovered. The client was `Event Machine` application connecting to the stud with `start_tls` (as described in EM documentation)....
"is that valid in TLS protocol?" - I don't know. I am not a security speciality neither. I will just let wireshark speak for myself. Both are screenshots from communication...
The workaround is to use: ``` Rails.application.routes.draw do ``` in the engine routing file.