Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with
or
.
Download ZIP

Loading…

channel multiplexing #43

Open
morganchristiansson opened this Issue · 6 comments

6 participants

@morganchristiansson

This has been requested before in other forums and tickets (1. http://github.com/slact/nginx_http_push_module/issues#issue/40 and 2. http://forum.nginx.org/read.php?2,23916 ). I'm putting it in as a separate issue so that it's not forgotten and can be subscribed to.

Make it possible to be a member of multiple channels using only one connection. Like being in a chat with 3 people. I could open 3 long polling requests but would have to trick around with domain names due to the 2-connection limit then.

something like http://server/sub/?channel_id=channel1,channel23,channel42

@pearcewang

happy to see the project live again.
sad to find multiplexing still a plan.

@pearcewang

Still no progress about this issue? A chat room without private channel is unreasonable, I love this module: light and clean. Waiting for multiplexing function to replace my current fat, hard to management chat room.

thanks a lot.

@grenzr

Like pearcewang, I really like the work you've done, but I'd really love multiplexing to be completed too.. Are you able to provide an update on whats happening (or not) with it?

thanks for your work so far - please keep this project alive, its great!

@caruccio

How is it going?

@rhapsodyv

It's alpha yet, but is working fine: https://github.com/rhapsodyv/nginx_http_push_module

@amcgregor

I multiplex and manage concurrent subscriptions upstream in my app. I have one channel per user with a message stream similar to:

[{act: 'msg', from: 'Bob', to: '#channel', msg: 'Howdy!'}]

[{act: 'ton', from: 'Jill', to: 'Bob'}]

[
    {act: 'toff', from: 'Jill', to: 'Bob'},
    {act: 'msg', from: 'Jill', to: 'Bob', msg: 'heroo?'}
]

[{act: 'msg', from: 'Eve', to: '#channel', msg: 'Why hello ther.'}]

The "multiple messages per message" is due to transactional management in my app. If multiple actions require notification they are compounded into a single message which the client just loops through. If the transaction fails (needs roll-back) the messages are eaten.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.