Hi, sorry for bad English. I looked at source, but it’s hard to read and understand in big project. But as i understood Discourse using own implementation of communication over (Long polling (only(?))) to represent most actual data to users with MessageBus, why? Why were not used Faye?

I too would be interested in a quick story about this architecture. I’m currently thinking how to best implement a chat (sorry, in PHP and not for Discourse), and a story about how you manage and route a large stream of messages would be very interesting. (Plus, in my case, I don’t know Ruby at all,…

As i know, to use Faye as a publish server, you can’t use Nginx or Apache as web server to proxy the Faye, so you need to publicize the Faye server to publish to client (it’s bad ?), in case of long polling, it works well with many kinds of web servers. Facebook uses long polling itself, i think lon…

The main feature of Faye and Socket.io etc… is distinguish the best transport according of capabilities of browser look here Faye: Simple pub/sub messaging for the web Persistent connections using WebSocket Long-polling via HTTP POST Cross Origin Resource Sharing Callback-polling via JSON-P

I wrote the message bus so I should answer this. However, before I answer anything let me explain the message bus. (in ruby code on the server) # publish the string norris to a channel called /chuck MessageBus.publish('/chuck', 'norris') # publish the string 'secret' to a channel called /check, b…

How does the message bus determine whether a particular message needs to be delivered to a particular recipient (who’s asking) or not? In other words - how does it keep track of security? Consider the situation: there’s a private conversation which you are invited to. There are 3 messages in the Me…

When you publish a message you specify who is allowed to see it: # only user id 100 will get secret santa MessageBus.publish('/secret', 'santa', user_ids: [100]) The middleware will not distribute messages to users who are not allowed to see them

[Bild] sam: # subscribe to the channel '/chuck' on the server MessageBus.subscribe('/chuck') do |msg| Forgive my lack of rails knowledge, but can you talk about the nuts and bolts of how this works? Does the handler proc run on a thread that is dedicated to getting MessageBus notifications? …

The api has a blocking subscribe for the less brave, Discourse supports multi threading even in a multi tenanted case. In fact we patch Active Record to support it. Allow connection_handler to be overriden per-thread by SamSaffron · Pull Request #8368 · rails/rails · GitHub Message bus is aware of …

[Bild] sam: When you publish a message you specify who is allowed to see it: Doesn’t this result in some rather long lists of user id’s attached to messages? Also - how is this stored in the DB? Table allowances(message_id, user_id)? For a long list of IDs that would mean a lot of INSERT’s, n…

How discourse stays online (Message Bus, Faye, Long Polling)

Entwickler

oganer (Руслан Корнев) 17. Februar 2013 um 04:43 6

It’s a client side https://github.com/discourse/discourse/blob/master/app/assets/javascripts/discourse/components/message_bus.js.coffee i’m interesting in server side.

Thema		Antworten	Aufrufe
Long Polling Message Bus Notifications from React Application Development	4	1385	27. Februar 2020
Message-bus is duplicating headers in Discourse chat Development chat , rest-api	6	547	13. Februar 2024
How does Discourse update the client on new posts from the server? Development	2	1093	15. Februar 2019
MessageBus - How to setup Messagebus using Dart-Flutter Development	3	1256	27. Februar 2025
MessageBus short polling is not working Bug	11	2867	29. September 2017

How discourse stays online (Message Bus, Faye, Long Polling)

Verwandte Themen