rack-devel archive mirror (unofficial) https://groups.google.com/group/rack-devel
 help / color / mirror / Atom feed
From: Ivan Aleksandrovich <intale.a@gmail.com>
To: rack-devel@googlegroups.com
Subject: SSE stops working after updating rack version to 1.4.3
Date: Wed, 9 Jan 2013 06:22:55 -0800 (PST)	[thread overview]
Message-ID: <3dda6773-08f6-4c8c-9415-0eaffa938969@googlegroups.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1187 bytes --]

Hi there. I want to notice that after updating rack version from 1.4.1 to 
1.4.3 the simple implementation of SSE stoped working for me(see 
application example in the attachment).
Gem list when that example works:

bundler (1.2.2)
daemons (1.1.8)
eventmachine (0.12.10)
haml (3.1.7)
rack (1.4.1)
rack-protection (1.2.0)
rake (10.0.2)
rubygems-bundler (1.1.0)
rvm (1.11.3.5)
sinatra (1.3.3)
thin (1.5.0)
tilt (1.3.3)

Gem list when that example doesn't work:
bundler (1.2.2)
daemons (1.1.8)
eventmachine (0.12.10)
haml (3.1.7)
rack (1.4.3)
rack-protection (1.2.0)
rake (10.0.2)
rubygems-bundler (1.1.0)
rvm (1.11.3.5)
sinatra (1.3.3)
thin (1.5.0)
tilt (1.3.3)

My environment:
 - Ruby version is ruby 1.9.3p327 (2012-11-10 revision 37606) [x86_64-linux]
 - Ubuntu 12.04 (precise) 64-bit, Linux 3.2.0-35-generic, GNOME 3.4.2
 - Firefox 18.0
What do I mean by SSE doesn't work? - It tries to reconnect forever(with 
delay of a few seconds which is default for EventSource implementation - 
see http://www.w3.org/TR/eventsource/#the-eventsource-interface for me 
info, reconnection time option). You may see these reconnection retries in 
server logs or by opening "Network" tab in firebug

[-- Attachment #2: Type: text/html, Size: 1308 bytes --]

             reply	other threads:[~2013-01-09 15:43 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-09 14:22 Ivan Aleksandrovich [this message]
2013-01-10  2:21 ` SSE stops working after updating rack version to 1.4.3 James Tucker
2013-01-10  9:55   ` Ivan Aleksandrovich

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-list from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://groups.google.com/group/rack-devel

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3dda6773-08f6-4c8c-9415-0eaffa938969@googlegroups.com \
    --to=rack-devel@googlegroups.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).