Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Pusher - Realtime client push service powered by websockets

pusherapp.com

Post reply on HN
Print view View original

1–10 of 23 posts

Re: Pusher - Realtime client push service powered by websockets

#2

Post by a-priori »

Oh, fun :) I'm just about to launch a similar service, called Zeropoll. It seems you're pushing the event-handling logic to the client side, whereas Zeropoll generates Javascript on the server (ala RJS) and pushes that to the client.

Your demo apps are great, by the way. Just curious, what's your business model going to be?

Re: Pusher - Realtime client push service powered by websockets

#4

Post by andr »

This is great, I was thinking about making a similar app, but never got around to it.

I'd love a simple ACL for channels. For example, you could do S3-style channel+timestamp+hash authentication, with the hash generated on the server with a secret key. Then for every channel I'd have channel17@r for read-only access, channel17@w for write-only, and channel17 for rw access (default). The way I understand the current system once I have the key for a channel I have unlimited access to it forever.

Re: Pusher - Realtime client push service powered by websockets

#7

Post by aaronblohowiak »

andr wrote: post #4

This is great, I was thinking about making a similar app, but never got around to it. I'd love a simple ACL for channels. For example, you could do S3-style channel+timestamp+hash authentication, with the hash generated on the server with a secret key. Then for every channel I'd have channel17@r for read-only access, channel17@w for write-only, and channel17 for rw access (default). The way I understand the current s…

I am working on something exactly like this, but as an open-source NodeJS project.. it lets you define a parameter (by default, session_id) and then checks a memcache instance for that key, and uses that to get access to channels with a specific prefix (by default "user:")... so you can have a channel "user:34343". This shoves authentication back into your app with the only dependency being a memcache instance shared by the NodeJS server and the web server. All of the other communication is similarly RESTful. if you want an email when i've got more to show, let me know.

Re: Pusher - Realtime client push service powered by websockets

#9

Post by dctanner »

Tawheed wrote: post #3

This is really awesome; except as an app developer, I really rather get a library that I own and have on my own infrastructure than a SaaS model, especially for something so critical to my application.

It depends on the type of app you're building. We built Pusher to complement existing AJAX workflows and make adding collaboration easy. There's lots more you can do with it though.

Re: Pusher - Realtime client push service powered by websockets

#10

Post by dctanner »

a-priori wrote: post #2

Oh, fun :) I'm just about to launch a similar service, called Zeropoll. It seems you're pushing the event-handling logic to the client side, whereas Zeropoll generates Javascript on the server (ala RJS) and pushes that to the client. Your demo apps are great, by the way. Just curious, what's your business model going to be?

When we're out of beta we will be offering several plans, probably limiting the max clients. There will always be a free plan though :)
Post reply on HN