Login or Register to Ask a Question and Join Our Community

Sponsored Content
Full Discussion: PubNub Live Chat Beta Testing
The Lounge What is on Your Mind? PubNub Live Chat Beta Testing Post 303034868 by Neo on Wednesday 8th of May 2019 11:12:18 AM
Old 05-08-2019
No Craig,

We are not calling hereNow every 300 ms.

LOL The function in updated() does not even fire, as I described. I don't think you fully understand how Vue.js lifecycle hooks or the JavaScript debounce() function works.

The updated() lifecycle hook in Vue.js only fires when there is a Vue.js event. In this code, that means it on fires on the events I described above.

Even when update() fires, the debounce() function does not fire because it fires only on the trailing edge of 300 ms and that function does not exist (the instance) because the update() lifecycle hook has already exited.

As I said above, that line of code does NOTHING. And in the current version running, it is commented out, since it does nothing.

Regarding PUBNUB.

Frankly, I feel in your replies that you may not fully understand your own API. Perhaps you have not actually every analyzed the XHR calls in DevTools looking at the code under various conditions? It seems you are advsing me from theory (from reading the API docs), not practice (coding and doing the analysis of the XHR calls).

Your API polls presence interval is based on subscribe() (presence set to TRUE). That is not the same as from the pubnub listener. It does not set the presence polling interval.

Yes, the listener listens but the polling is fired every second based in the client when presence is set to TRUE in subscribe.

I have already analyzed these API calls in Chrome Dev tools and it's easy to see what is going on,

You seem to not understand that your API polls presence every second (when it is set in subscribe to TRUE) and there is no way to set that interval in your API.

This generates 100s of thousands of useless transactions because every subscriber is polling the pubnub network every second or so when the subscribe presence TRUE.

I have been over this very carefully in Chome DevTools watching how each flag effects the XHR calls.

Then, again, I could be wrong, LOL... but I have been over this very carefully in Chrome DevTools many times for hours.
 

4 More Discussions You Might Find Interesting

1. Solaris

Live Chat For 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 Quick Video Overview of PubNub Live Chat @UNIX.com (version 0.7614)

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?

Live Chat (Alpha) in UserCP SF 0.7517

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

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 SUSE

crmd

CRM 
DAEMON(8)						      Pacemaker Configuration						     CRM DAEMON(8)

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] [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 [60s]
	   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.

       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 					    07/05/2010							     CRM DAEMON(8)
All times are GMT -4. The time now is 04:14 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy