1

Closed

Pusher.com events not reaching device

description

From an email I sent to Pusher.com's tech folks:
 
 
Hi Phil, I’ve been working on getting web sockets implemented for the .net micro framework. Have made some progress. We are finally able to connect to Pusher from an embedded device, which is awesome. Project hosted here:
http://microcontrib.codeplex.com/
 
However, I’m not seeing messages pushed to my device when sending from the web based test form (on Pusher.com). I’m thinking there might be some undocumented javascript handshake that happens before Pusher.com will start sending events, is that correct? If so can you help me understand that sequence?
 
I’d encourage you guys to think about your service as a WebSocket service for any computing platform, not just JavaScript. I understand the majority of excitement about websockets today is from the web development community, but I see value in other contexts as well (like embedded computing for example).
 
Anyway, here is what I’m seeing (trace from the wire):
 
GET /app/765ec374ae0a69f4ce44?client=js&version=1.8.5 HTTP/1.1
Upgrade: WebSocket
Connection: Upgrade
Host: ws.pusherapp.com
Origin: http://pusher.com
Sec-WebSocket-Key1: T64 223 ;6266
Sec-WebSocket-Key2: t 3 4V2435*\ 978y vv6
 
.......B
 
HTTP/1.1 101 WebSocket Protocol Handshake
Upgrade: WebSocket
Connection: Upgrade
Sec-WebSocket-Location: ws://ws.pusherapp.com/app/765ec374ae0a69f4ce44?client=js&version=1.8.5
Sec-WebSocket-Origin: http://pusher.com
 
......#..%..?.l..{"event":"pusher:connection_established","data":"{\"socket_id\":\"1165.776810\"}"}..{"event":"pusher:subscribe","data":{"channel":"LcbU9ctL"}}.
 
 
Obviously Pusher is telling me I’ve connected and gave me a socket id. It looks like it also gave me a channel (which seems to be a random string). What should I do with that channel id, if anything?
 
Thanks, Paul

file attachments

Closed Jul 3, 2011 at 3:55 AM by juliusfriedman

comments

coolpablo wrote Jun 28, 2011 at 5:20 PM

I think I figured out what we need to do next. After connecting, we need to send a JSON object telling pusher what channel to send events to. See attached image.

wrote Jul 3, 2011 at 3:55 AM

Resolved with changeset 80177.

wrote Feb 13, 2013 at 8:31 PM

wrote May 15, 2013 at 4:00 AM