|
|
Sponsored Content
The Lounge
What is on Your Mind?
PubNub Live Chat Beta Testing
Post 303034872 by pubnubcraig on Wednesday 8th of May 2019 11:54:48 AM
05-08-2019
I don't use Vue.js and I have never heard of the debounce API. Neither is specific PubNub and there are dozens of JS frameworks out there so not possible, or necessary, to know them all.
I still think PubNub needs a new configuration parameter in subscribe() which sets the polling interval for presence, but let me take another look tomorrow since you have made some changes in our configuration and see if I set subscribe presence to TRUE in my code (it is current set to FALSE), if it keeps polling and polling like crazy.
Subscribe already has an interval, it is the subscribeTimeout config, that you can set in the PubNub init, but please do not. It should only be changed for very specific reasons, that I will not get into right now. You will only cause your app to have increased transactions at no additional upside or cause your app to break depending on whether you set it shorter or longer. The default subscribeTimeout is 280s, and this is exactly the same for listening to presence events because it is on the subscribe connection. The hereNow is a completely different API and a different connection which does not work on the subscribe connection.
When you subscribe withPresence:true, you are just adding presence channels (with the -pnpres suffix) to the list of subscribed channels. When another person subscribes to that channel, those listening to presence events (withPresence:true) on that channel will receive that presence event, in realtime, not on some polling cycle.
But see my response about Announce Max. The increased transaction were self-inflicted
Not that you would have known the side effects but rarely does anyone change that setting.
And I just checked the chat app again. It appears you upgraded to lastest PubNub JS SDK version - cheers - and I see that the client is not having the 10s interval response anymore. At most it will be 280s or everytime someone joins, leaves, timeouts, or a message is published and therefore received.
Cheers
Craig
I still think PubNub needs a new configuration parameter in subscribe() which sets the polling interval for presence, but let me take another look tomorrow since you have made some changes in our configuration and see if I set subscribe presence to TRUE in my code (it is current set to FALSE), if it keeps polling and polling like crazy.
Subscribe already has an interval, it is the subscribeTimeout config, that you can set in the PubNub init, but please do not. It should only be changed for very specific reasons, that I will not get into right now. You will only cause your app to have increased transactions at no additional upside or cause your app to break depending on whether you set it shorter or longer. The default subscribeTimeout is 280s, and this is exactly the same for listening to presence events because it is on the subscribe connection. The hereNow is a completely different API and a different connection which does not work on the subscribe connection.
When you subscribe withPresence:true, you are just adding presence channels (with the -pnpres suffix) to the list of subscribed channels. When another person subscribes to that channel, those listening to presence events (withPresence:true) on that channel will receive that presence event, in realtime, not on some polling cycle.
But see my response about Announce Max. The increased transaction were self-inflicted
Not that you would have known the side effects but rarely does anyone change that setting.And I just checked the chat app again. It appears you upgraded to lastest PubNub JS SDK version - cheers - and I see that the client is not having the 10s interval response anymore. At most it will be 280s or everytime someone joins, leaves, timeouts, or a message is published and therefore received.
Cheers
Craig
This User Gave Thanks to pubnubcraig For This Post:
|
|
4 More Discussions You Might Find Interesting
1. Solaris
Does anyone know of any online live chat discussion groups for Solaris? If so, please let me know... Thanks!
Rob Sandifer (3 Replies)
Discussion started by: RobSand
3 Replies
2. What is on Your Mind?
A number of people have asked me to make some videos, so I just got my first condenser microphone and so I can make some amateurish screen casts. I will try to do better in the future.
A quick overview of PubNub Live Chat @unix.com
The video is best is you set the Quality to HD 1080. The... (0 Replies)
Discussion started by: Neo
0 Replies
3. What is on Your Mind?
Interesting....
I am still working on the kinks for Live Chat here at unix.com using a publish-subscribe API from PubNub. Two days ago while working on it, a new user joined the live chat and asked about how to post a new thread in the forum. Then today, one of the members of the PubNub team... (23 Replies)
Discussion started by: Neo
23 Replies
4. What is on Your Mind?
Update: UserCP Screeching Frog 0.7641 - Changed Live Chat to Live Updates
In this version of the UserCP, I have changed "Live Chat" to "Live Updates" by disabling the ability to post in the "live chat" area and changed the name to "Live Updates"
The reason for this change is that experienced... (6 Replies)
Discussion started by: Neo
6 Replies
LEARN ABOUT DEBIAN
crmd
CRM
DAEMON(7) Pacemaker Configuration CRM DAEMON(7) NAME
crmd - CRM Daemon Options SYNOPSIS
[dc-version=string] [cluster-infrastructure=string] [dc-deadtime=time] [cluster-recheck-interval=time] [election-timeout=time] [shutdown-escalation=time] [crmd-integration-timeout=time] [crmd-finalization-timeout=time] [crmd-transition-delay=time] [expected-quorum-votes=integer] DESCRIPTION
This is a fake resource that details the options that can be configured for the CRM Daemon. SUPPORTED PARAMETERS
dc-version = string [none] Version of Pacemaker on the cluster's DC. Includes the hash which identifies the exact Mercurial changeset it was built from. Used for diagnostic purposes. cluster-infrastructure = string [heartbeat] The messaging stack on which Pacemaker is currently running. Used for informational and diagnostic purposes. dc-deadtime = time [20s] How long to wait for a response from other nodes during startup. The "correct" value will depend on the speed/load of your network and the type of switches used. cluster-recheck-interval = time [15min] Polling interval for time based changes to options, resource parameters and constraints. The Cluster is primarily event driven, however the configuration can have elements that change based on time. To ensure these changes take effect, we can optionally poll the cluster's status for changes. Allowed values: Zero disables polling. Positive values are an interval in seconds (unless other SI units are specified. eg. 5min) election-timeout = time [2min] *** Advanced Use Only ***. If need to adjust this value, it probably indicates the presence of a bug. shutdown-escalation = time [20min] *** Advanced Use Only ***. If need to adjust this value, it probably indicates the presence of a bug. crmd-integration-timeout = time [3min] *** Advanced Use Only ***. If need to adjust this value, it probably indicates the presence of a bug. crmd-finalization-timeout = time [30min] *** Advanced Use Only ***. If you need to adjust this value, it probably indicates the presence of a bug. crmd-transition-delay = time [0s] *** Advanced Use Only *** Enabling this option will slow down cluster recovery under all conditions Delay cluster recovery for the configured interval to allow for additional/related events to occur. Useful if your configuration is sensitive to the order in which ping updates arrive. expected-quorum-votes = integer [2] The number of nodes expected to be in the cluster Used to calculate quorum in openais based clusters. AUTHOR
Andrew Beekhof <andrew@beekhof.net> Author. Pacemaker Configuration 04/17/2012 CRM DAEMON(7)