Rainbows! Rack HTTP server user/dev discussion
 help / color / mirror / Atom feed
* Upgrading websocket application with Rainbows
@ 2013-03-25 23:59 Cary Cherng
       [not found] ` <CAPxkqHg7RtPMRXDd-KCoK8b63opM3DdBFVBP9QAq2HOJBvD5_g-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
  0 siblings, 1 reply; 2+ messages in thread
From: Cary Cherng @ 2013-03-25 23:59 UTC (permalink / raw)
  To: rainbows-talk-GrnCvJ7WPxnNLxjTenLetw

Is there a best practice for how to restart a Rails app that uses websockets?

As far as I can tell, the Rainbows documentation doesn't say anything
about how to deal with existing websocket connections when using
signal handling to replace old processes with new ones.
_______________________________________________
Rainbows! mailing list - rainbows-talk-GrnCvJ7WPxnNLxjTenLetw@public.gmane.org
http://rubyforge.org/mailman/listinfo/rainbows-talk
Do not quote signatures (like this one) or top post when replying


^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: Upgrading websocket application with Rainbows
       [not found] ` <CAPxkqHg7RtPMRXDd-KCoK8b63opM3DdBFVBP9QAq2HOJBvD5_g-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
@ 2013-03-26  0:13   ` Eric Wong
  0 siblings, 0 replies; 2+ messages in thread
From: Eric Wong @ 2013-03-26  0:13 UTC (permalink / raw)
  To: Rainbows! list

Cary Cherng <ccherng-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:
> Is there a best practice for how to restart a Rails app that uses websockets?
> 
> As far as I can tell, the Rainbows documentation doesn't say anything
> about how to deal with existing websocket connections when using
> signal handling to replace old processes with new ones.

Unfortunately, there isn't one that I know of.

I haven't looked at WebSockets in ages, but I think client-side code
needs to be taught to handle disconnects/shutdowns gracefully and retry
as needed.
_______________________________________________
Rainbows! mailing list - rainbows-talk-GrnCvJ7WPxnNLxjTenLetw@public.gmane.org
http://rubyforge.org/mailman/listinfo/rainbows-talk
Do not quote signatures (like this one) or top post when replying


^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2013-03-26  0:14 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2013-03-25 23:59 Upgrading websocket application with Rainbows Cary Cherng
     [not found] ` <CAPxkqHg7RtPMRXDd-KCoK8b63opM3DdBFVBP9QAq2HOJBvD5_g-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2013-03-26  0:13   ` Eric Wong

Rainbows! Rack HTTP server user/dev discussion

This inbox may be cloned and mirrored by anyone:

	git clone --mirror https://yhbt.net/rainbows-public
	git clone --mirror http://ou63pmih66umazou.onion/rainbows-public

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V1 rainbows-public rainbows-public/ https://yhbt.net/rainbows-public \
		rainbows-public@yhbt.net rainbows-public@bogomips.org rainbows-talk@rubyforge.org rainbows-talk-GrnCvJ7WPxnNLxjTenLetw@public.gmane.org
	public-inbox-index rainbows-public

Example config snippet for mirrors.
Newsgroups are available over NNTP:
	nntp://news.public-inbox.org/inbox.comp.lang.ruby.rainbows
	nntp://ou63pmih66umazou.onion/inbox.comp.lang.ruby.rainbows
 note: .onion URLs require Tor: https://www.torproject.org/

code repositories for the project(s) associated with this inbox:

	../../../rainbows.git

AGPL code for this site: git clone http://ou63pmih66umazou.onion/public-inbox.git