After client connects and a single op is submitted; no further ops are sent

[Gurdas Nijor]

Here's a screenshot of the network tab after the final op that was able to be submitted goes through:

Here's the detailed request/response info for that final op before the connection goes silent (even though the client is showing as subscribed, no data comes in via subscription either):

Remote Address:165.225.129.253:80
Request URL:http://reaxer.nodejitsu.com/channel/bind?a=99ig5ibghtfj&VER=8&SID=1eeyr2cm&RID=31528&AID=3&zx=1lvp72yv7fmc&t=1
Request Method:POST
Status Code:200 OK

**Request Headers**

Accept:*/*
Accept-Encoding:gzip,deflate,sdch
Accept-Language:en-US,en;q=0.8
Cache-Control:no-cache
Connection:keep-alive
Content-Length:190
Content-Type:application/x-www-form-urlencoded
Cookie:_cb_ls=1; __utma=249701125.661083566.1397924491.1398022791.1398026923.4; __utmc=249701125; __utmz=249701125.1397924491.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); _chartbeat2=BSc/4pV9HPiDQbgfv.1397924491010.1398026922974.11; _chartbeat_uuniq=3; jitsu.id=s%3AC8F7ffw8StyLuZ0EsRGsSaYj.rIJHHlJQxRu3l9U%2BvwBkhA5vHgRiQcH0LCi87Zcufu4
Host:reaxer.nodejitsu.com
Origin:http://reaxer.nodejitsu.com
Pragma:no-cache
Referer:http://reaxer.nodejitsu.com/
User-Agent:Mozilla/5.0 (Macintosh; Intel Mac OS X 10_9_2) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/36.0.1948.0 Safari/537.36

**Query String Parameters**
a:99ig5ibghtfj
VER:8
SID:1eeyr2cm
RID:31528
AID:3
zx:1lvp72yv7fmc
t:1

**Form Data**
count:1
ofs:1
req0_JSON:{"a":"op","v":1388,"op":[{"p":[170],"si":"f"}],"c":"projects","d":"freetextfield"}


**Response Headers**
cache-control:no-cache, no-store, max-age=0, must-revalidate
connection:keep-alive
content-type:text/plain
date:Thu, 24 Apr 2014 07:18:28 GMT
expires:Fri, 01 Jan 1990 00:00:00 GMT
pragma:no-cache
transfer-encoding:chunked
x-content-type-options:nosniff
x-powered-by:Express

**Response Data**

7
[1,3,0]

Strangely enough; everything seems to work for the first 20 minutes after I deploy; the collaborative textarea i'm trying to test with correctly sends the transform data over the wire and keeps multiple instances of it in sync (I'm using racer as my backend if that helps, so i'm not sure which layer (racer/share/livedb, or if its an issue with nodejitsu that i'm not aware of)

[Gurdas Nijor]

Closing, since this seems to be more a hosting issue than a sharejs issue specifically