Sponsored Content
The Lounge What is on Your Mind? PubNub Live Chat Beta Testing Post 303034869 by pubnubcraig on Wednesday 8th of May 2019 11:32:29 AM
Old 05-08-2019
Neo -

I just ran the chat app (should have done that first) and I see what is causing the every 10s transaction. Your Presence add-on has a Presence Interval of 10s (that is the default) and you set your Announce Max property to 1, that's 1 channel occupant (20 is the default). So PubNub is sending an update every 10s.

Announce Max
Once the number of occupants reaches this number, join, leave and timeout events are no longer sent as realtime presence events to those listening (subscribed withPresence:true). Instead, PubNub Network will send an occupancy count every 10s (or whatever the value is for the Interval property). If you want to know who join, leave, timeout since the last interval update, you need to enable Presence Deltas.

My recommendation: set Announce Max back to 20. A different number may be better, but that should suffice for now. Rarely is this value ever changed for most apps. I took the liberty of updating this property to 20 to prevent your account from accumulating needless transactions. They were not benefitting your app in the slightest anyways. You would need to enable Presence Deltas for that Announce Max = 1 setting to be useful and then you would have to handle the presence delta event payload in your client app, which I don't think you are doing at the moment. You can set this back to 1 if you feel that is what you need.

Let's schedule time for a PubNub overview session and I can give you all the ins and outs, gotchas, best practices and how it works under the covers so you can make the best informed decisions with your implementation. I know I can save you hours of frustration and you'll appreciate how this all works much more.

Cheers
Craig

--- Post updated at 03:32 PM ---

Tim - I understand our APIs quite well. Your app, not so much, admittedly. Not a Vue expert. See my last post.
This User Gave Thanks to pubnubcraig For This Post:
 

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
Plack::Builder(3pm)					User Contributed Perl Documentation				       Plack::Builder(3pm)

NAME
Plack::Builder - OO and DSL to enable Plack Middlewares SYNOPSIS
# in .psgi use Plack::Builder; my $app = sub { ... }; builder { enable "Deflater"; enable "Session", store => "File"; enable "Debug", panels => [ qw(DBITrace Memory Timer) ]; enable "+My::Plack::Middleware"; $app; }; # use URLMap builder { mount "/foo" => builder { enable "Foo"; $app; }; mount "/bar" => $app2; mount "http://example.com/" => builder { $app3 }; }; # using OO interface my $builder = Plack::Builder->new(); $builder->add_middleware('Foo', opt => 1); $app = $builder->mount('/app' => $app); $app = $builder->to_app($app); DESCRIPTION
Plack::Builder gives you a quick domain specific language (DSL) to wrap your application with Plack::Middleware subclasses. The middleware you're trying to use should use Plack::Middleware as a base class to use this DSL, inspired by Rack::Builder. Whenever you call "enable" on any middleware, the middleware app is pushed to the stack inside the builder, and then reversed when it actually creates a wrapped application handler. "Plack::Middleware::" is added as a prefix by default. So: builder { enable "Foo"; enable "Bar", opt => "val"; $app; }; is syntactically equal to: $app = Plack::Middleware::Bar->wrap($app, opt => "val"); $app = Plack::Middleware::Foo->wrap($app); In other words, you're supposed to "enable" middleware from outer to inner. INLINE MIDDLEWARE
Plack::Builder allows you to code middleware inline using a nested code reference. If the first argument to "enable" is a code reference, it will be passed an $app and is supposed to return another code reference which is PSGI application that consumes $env in runtime. So: builder { enable sub { my $app = shift; sub { my $env = shift; # do preprocessing my $res = $app->($env); # do postprocessing return $res; }; }; $app; }; is equal to: my $mw = sub { my $app = shift; sub { my $env = shift; $app->($env) }; }; $app = $mw->($app); URLMap support Plack::Builder has a native support for Plack::App::URLMap with "mount" method. use Plack::Builder; my $app = builder { mount "/foo" => $app1; mount "/bar" => builder { enable "Foo"; $app2; }; }; See Plack::App::URLMap's "map" method to see what they mean. With builder you can't use "map" as a DSL, for the obvious reason :) NOTE: Once you use "mount" in your builder code, you have to use "mount" for all the paths, including the root path ("/"). You can't have the default app in the last line of "builder" like: my $app = sub { my $env = shift; ... }; builder { mount "/foo" => sub { ... }; $app; # THIS DOESN'T WORK }; You'll get warnings saying that your mount configuration will be ignored. Instead you should use "mount "/" => ..." in the last line to set the default fallback app. builder { mount "/foo" => sub { ... }; mount "/" => $app; } Note that the "builder" DSL returns a whole new PSGI application, which means o "builder { ... }" should normally the last statement of a ".psgi" file, because the return value of "builder" is the application that actually is executed. o You can nest your "builder" block, mixed with "mount" (see URLMap support above): builder { mount "/foo" => builder { mount "/bar" => $app; } } will locate the $app under "/foo/bar" since the inner "builder" block puts it under "/bar" and it results a new PSGI application which is located under "/foo" because of the outer "builder" block. CONDITIONAL MIDDLEWARE SUPPORT
You can use "enable_if" to conditionally enable middleware based on the runtime environment. See Plack::Middleware::Conditional for details. SEE ALSO
Plack::Middleware Plack::App::URLMap Plack::Middleware::Conditional perl v5.14.2 2012-05-17 Plack::Builder(3pm)
All times are GMT -4. The time now is 08:37 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy