Sponsored Content
Full Discussion: PubNub PHP SDK V4 Issues
Top Forums Web Development PubNub PHP SDK V4 Issues Post 303034633 by hbmangal on Wednesday 1st of May 2019 10:25:58 AM
Old 05-01-2019
Code is working fine

Hey Neo,


There is some special character with the line require and it is giving error:
Code:
require_once('vendor/autoload.php');

Code:
See below code, it is working for me:
require_once('vendor/autoload.php');

use PubNub\PubNub;
use PubNub\Enums\PNStatusCategory;
use PubNub\Callbacks\SubscribeCallback;
use PubNub\PNConfiguration;
 
class MySubscribeCallback extends SubscribeCallback {
    function status($pubnub, $status) {
        if ($status->getCategory() === PNStatusCategory::PNUnexpectedDisconnectCategory) {
            // This event happens when radio / connectivity is lost
        } else if ($status->getCategory() === PNStatusCategory::PNConnectedCategory) {
            // Connect event. You can do stuff like publish, and know you'll get it
            // Or just use the connected event to confirm you are subscribed for
            // UI / internal notifications, etc
        } else if ($status->getCategory() === PNStatusCategory::PNDecryptionErrorCategory) {
            // Handle message decryption error. Probably client configured to
            // encrypt messages and on live data feed it received plain text.
        }
    }
 
    function message($pubnub, $message) {
        // Handle new message stored in message.message
    }
 
    function presence($pubnub, $presence) {
        // handle incoming presence data
    }
}
 
$pnconf = new PNConfiguration();
$pubnub = new PubNub($pnconf);

$pnconf->setSubscribeKey("demo");
$pnconf->setPublishKey("demo");
$subscribeCallback = new MySubscribeCallback();
$pubnub->addListener($subscribeCallback);
 
// Subscribe to a channel, this is not async.
$pubnub->subscribe()
    ->channels("hello_world")
    ->execute();
 
// Use the publish command separately from the Subscribe code shown above.
// Subscribe is not async and will block the execution until complete.
$result = $pubnub->publish()
              ->channel("hello_world")
              ->message("Hello PubNub")
              ->sync();
 
print_r($result);

Happy coding Smilie
This User Gave Thanks to hbmangal For This Post:
 

8 More Discussions You Might Find Interesting

1. OS X (Apple)

iPhone SDK?

Just need a little help learning to code using the iPhone SDK. HELP WOULD BE GREAT!!! (1 Reply)
Discussion started by: Nintenman
1 Replies

2. Programming

SDK For cdwriter

I have a problem. I try to write a cd writer program ins c# but I can't find any sdk. Any one who knows? Thank you in advance :) (5 Replies)
Discussion started by: cs05pp2
5 Replies

3. Shell Programming and Scripting

issues with simplexml_load_string/SimpleXMLElement on PHP 5.1/Linux

This works fine under WAMP with PHP 5.3 and Windows XP on my dev machine. But on a Unix/PHP 5.1 env it doesn't. I am looking to pull out "LineNumber" and "TaxAmount" from the XML for each iteration of the loop below, for each iteration "$tax_line" is always an object of simplexml_load_string (... (0 Replies)
Discussion started by: crmpicco
0 Replies

4. UNIX for Advanced & Expert Users

Autosys-SDK

Hi friends, I am trying to validate the jil file programmatically. I plan to use the SDK provided by Autosys. Is CA provide any interfaces for this? Another thing : What is Jil syntax checker or Jil verifier or Jil validator? Where is it available in autosys? I am using R11 SP2 version... (0 Replies)
Discussion started by: ksswamy
0 Replies

5. Solaris

error during the installation SDK 6

Dear Members, this java already install in my machine $ uname -a SunOS maxdmail.com 5.10 Generic_139556-08 i86pc i386 i86pc $ java -version java version "1.5.0_17" Java(TM) Platform, Standard Edition for Business (build 1.5.0_17-b04) Java HotSpot(TM) Client VM (build 1.5.0_17-b04,... (1 Reply)
Discussion started by: xxmasrawy
1 Replies

6. AIX

Compile PHP in AIX: Loading issues

Finally I was able to compile PHP on AIX. When I try to load from Apache, I get the below error. /install/usr/local/apache2/bin:>apachectl -f /install/usr/local/apache2/conf/httpd.conf -k stop httpd: Syntax error on line 53 of /install/usr/local/apache2/conf/httpd.conf: Cannot load... (0 Replies)
Discussion started by: KarthikKannan
0 Replies

7. 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

8. What is on Your Mind?

PubNub Live Chat Beta Testing

Dear All, We are now beta testing our future "Live Chat" area using PubNub technology. https://community.unix.com/ This purpose of this testing is to test the core system, in general, and to see how many, if any, bugs crawl out of the woodwork. This "Live Chat" is not the... (48 Replies)
Discussion started by: Neo
48 Replies
mosquitto_pub(1)														  mosquitto_pub(1)

NAME
mosquitto_pub - an mqtt version 3.1 client for publishing simple messages SYNOPSIS
mosquitto_pub [-d] [-h hostname] [-i client_id] [-I client id prefix] [-p port number] [-q message QoS] [--quiet] [-r] { -f file | -l | -m message | -n | -s} [ -u username [-P password] ] [ --will-topic topic [--will-payload payload] [--will-qos qos] [--will- retain] ] -t message-topic DESCRIPTION
mosquitto_pub is a simple mqtt version 3.1 client that will publish a single message on a topic and exit. OPTIONS
-d, --debug Enable debug messages. -f, --file Send the contents of a file as the message. -h, --host Specify the host to connect to. Defaults to localhost. -i, --id The id to use for this client. If not given, defaults to mosquitto_pub_ appended with the process id of the client. Cannot be used at the same time as the --id-prefix argument. -I, --id-prefix Provide a prefix that the client id will be built from by appending the process id of the client. This is useful where the broker is using the clientid_prefixes option. Cannot be used at the same time as the --id argument. -l, --stdin-line Send messages read from stdin, splitting separate lines into separate messages. Note that blank lines won't be sent. -m, --message Send a single message from the command line. -n, --null-message Send a null (zero length) message. -p, --port Connect to the port specified instead of the default 1883. -P, --pw Provide a password to be used for authenticating with the broker. Using this argument without also specifying a username is invalid. This requires a broker that supports MQTT v3.1. See also the --username option. -q, --qos Specify the quality of service to use for the message, from 0, 1 and 2. Defaults to 0. --quiet If this argument is given, no runtime errors will be printed. This excludes any error messages given in case of invalid user input (e.g. using --port without a port). -r, --retain If retain is given, the message will be retained as a "last know good" value on the broker. See mqtt(7) for more information. -s, --stdin-file Send a message read from stdin, sending the entire content as a single message. -t, --topic The mqtt topic on which to publish the message. See mqtt(7) for more information on mqtt topics. -u, --username Provide a username to be used for authenticating with the broker. This requires a broker that supports MQTT v3.1. See also the --pw argument. --will-payload Specify a message that will be stored by the broker and sent out if this client disconnects unexpectedly. This must be used in con- junction with --will-topic. --will-qos The QoS to use for the Will. Defaults to 0. This must be used in conjunction with --will-topic. --will-retain If given, if the client disconnects unexpectedly the message sent out will be treated as a retained message. This must be used in conjunction with --will-topic. --will-topic The topic on which to send a Will, in the event that the client disconnects unexpectedly. WILLS
mosquitto_sub can register a message with the broker that will be sent out if it disconnects unexpectedly. See mqtt(7) for more informa- tion. The minimum requirement for this is to use --will-topic to specify which topic the will should be sent out on. This will result in a non- retained, zero length message with QoS 0. Use the --will-retain, --will-payload and --will-qos arguments to modify the other will parameters. EXAMPLES
Publish temperature information to localhost with QoS 1: o mosquitto_pub -t sensors/temperature -m 32 -q 1 Publish timestamp and temperature information to a remote host on a non-standard port and QoS 0: o mosquitto_pub -h 192.168.1.1 -p 1885 -t sensors/temperature -m "1266193804 32" Publish light switch status. Message is set to retained because there may be a long period of time between light switch events: o mosquitto_pub -r -t switches/kitchen_lights/status -m "on" Send the contents of a file in two ways: o mosquitto_pub -t my/topic -f ./data o mosquitto_pub -t my/topic -s < ./data Send parsed electricity usage data from a Current Cost meter, reading from stdin with one line/reading as one message: o read_cc128.pl | mosquitto_pub -t sensors/cc128 -l BUGS
mosquitto_pub bug information can be found at http://launchpad.net/mosquitto SEE ALSO
mqtt(7) mosquitto_sub(1) mosquitto(8) libmosquitto(3) AUTHOR
Roger Light <roger@atchoo.org> 5 February 2012 mosquitto_pub(1)
All times are GMT -4. The time now is 06:15 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy