Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update for socket.io v1.0 #75

Closed
wants to merge 5 commits into from
Closed

Conversation

calebboyd
Copy link

Followed pattern set forth by this adapter: socket.io-redis

@glennblock
Copy link
Contributor

Hi @calebboyd if you want to send this over here, I've forked it. https://github.com/Azure-contrib/socket.io-servicebus

@calebboyd
Copy link
Author

@glennblock sure thing!

@calebboyd calebboyd closed this Dec 8, 2014
@glennblock
Copy link
Contributor

Hi @calebboyd

Thanks! Not to be difficult but I am working to get this just transferred over to contrib in which case I'll delete my fork. If that happens, you'll need send another PR :-), also most likely to a diff branch.

I'll keep you posted in the next few days!

Glenn

@calebboyd calebboyd reopened this Apr 1, 2015
@glennblock
Copy link
Contributor

Thanks @calebboyd, we'll look into this now that we're in business.

@glennblock
Copy link
Contributor

@calebboyd does this support synchronizing the list of clients? Redis has a DB and does Pub Sub on top. Service Bus is purely message based. When we were implementing the SB Store, we had to handle this by sending messages between to synchronize the lists.

@glennblock
Copy link
Contributor

@calebboyd that was an issue with the chat sample app, not with the store itself.

On that note, did you look at the samples? Those are currently going to break if this PR is accepted. We need the samples to work.

@calebboyd
Copy link
Author

Yeah I can take a look at those. Also it looks like a client api was added for cross node client handling in the redis adapter . That will need to be looked at too. I've actually stopped using this in production (worked great when it was there), since azure added redis.

@glennblock
Copy link
Contributor

Glad to hear it worked well for you. Understood on redis.

I appreciate your effort here and your patience!

On Tue, Mar 31, 2015 at 6:44 PM Caleb Boyd notifications@github.com wrote:

Yeah I can take a look at those. Also it looks like a client api was added
for cross node client handling in the redis adapter
https://github.com/Automattic/socket.io-redis/blob/master/index.js#L150
. That will need to be looked at too. I've actually stopped using this in
production (worked great when it was there), since azure added redis.


Reply to this email directly or view it on GitHub
#75 (comment)
.

@shijuvar
Copy link

shijuvar commented Apr 1, 2015

This is really good thing that some updates are happening on this repository.

@glennblock
Copy link
Contributor

An on that note...I just realized Travis CI needs to get fixed.

@calebboyd calebboyd closed this Aug 28, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants