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);
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)
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)
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)
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)
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)
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
LEARN ABOUT DEBIAN
mosquitto_sub
mosquitto_sub(1)mosquitto_sub(1)NAME
mosquitto_sub - an mqtt version 3.1 client for subscribing to topics
SYNOPSIS
mosquitto_sub [-c] [-d] [-h hostname] [-i client_id] [-I client id prefix] [-k keepalive time] [-p port number] [-q message QoS] [--quiet]
[-v] [ -u username [-P password] ] [ --will-topic topic [--will-payload payload] [--will-qos qos] [--will-retain] ] -t
message topic ...
DESCRIPTION
mosquitto_sub is a simple mqtt version 3.1 client that will subscribe to a topic and print the messages that it receives.
OPTIONS -c, --disable-clean-session
Disable the 'clean session' flag. This means that all of the subscriptions for the client will be maintained after it disconnects,
along with subsequent QoS 1 and QoS 2 messages that arrive. When the client reconnects, it will receive all of the queued messages.
If using this option, it is recommended that the client id is set manually with --id
-d, --debug
Enable debug messages.
-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_sub_ 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.
-k, --keepalive
The number of seconds between sending PING commands to the broker for the purposes of informing it we are still connected and func-
tioning. Defaults to 60 seconds.
-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 desired for the incoming messages, from 0, 1 and 2. Defaults to 0. See mqtt(7) for more information
on QoS.
The QoS is identical for all topics subscribed to in a single instance of mosquitto_sub.
--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).
-t, --topic
The mqtt topic to subscribe to. See mqtt(7) for more information on mqtt topics.
This option may be repeated to subscribe to multiple 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.
-v, --verbose
Print received messages verbosely. With this argument, messages will be printed as "topic payload". When this argument is not given,
the messages are printed as "payload".
--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
Note that these really are examples - the subscriptions will work if you run them as shown, but there must be something publishing messages
on those topics for you to receive anything.
Subscribe to temperature information on localhost with QoS 1:
o mosquitto_sub -t sensors/temperature -q 1
Subscribe to hard drive temperature updates on multiple machines/hard drives. This expects each machine to be publishing its hard drive
temperature to sensors/machines/HOSTNAME/temperature/HD_NAME.
o mosquitto_sub -t sensors/machines/+/temperature/+
Subscribe to all broker status messages:
o mosquitto_sub -v -t $SYS/#
BUGS
mosquitto_sub bug information can be found at http://launchpad.net/mosquitto
SEE ALSO mqtt(7)mosquitto_pub(1)mosquitto(8)libmosquitto(3)AUTHOR
Roger Light <roger@atchoo.org>
5 February 2012 mosquitto_sub(1)
05-01-2019
