04-19-2019
Neo - thanks for working with us at PubNub Support. We are actively working on updating the Vue SDK Docs with at least an "OUTDATED" message in the short term and long term, a new Vue SDK that lives up to the JavaScript SDK. Not sure how that Vue SDK got released in that condition but again, thanks for vetting it and reporting back to us.
We'll (SDK engineer manager and I) be in touch with more very soon.
Cheers
Craig
This User Gave Thanks to pubnubcraig For This Post:
5 More Discussions You Might Find Interesting
1. Web Development
Hi,
I am trying to embed Skype or any other video chat/chat program into a webpage. Has anyone had success doing this? or know how?
Thanks
Phil (2 Replies)
Discussion started by: phil_heath
2 Replies
2. What is on Your Mind?
Working on the badging system, Just found this old thread for 2006 and started reading it. ROTFL ... what a great discussion between forum members and our chat bot Gollum "back in the good old days"... You must check this out if you want a laugh and big smile:
... (1 Reply)
Discussion started by: Neo
1 Replies
3. Web Development
Vue Router has some quirks and on of the quirks is that it is not reliable when adding external links using the vue-router library.
After struggling with many solutions, I have found that creating a simple Vue.js component like this one seems to work the best (so far):
Component Example: ... (0 Replies)
Discussion started by: Neo
0 Replies
4. Web Development
A number of people have asked me how to get started with Vue.js and my reply before today was to Google "Vue.js". That has changed and my recommendation to anyone who wants to learn the fastest growing, easiest to learn and use Vue.js web dev framework is to watch this video tutorial series:
... (0 Replies)
Discussion started by: Neo
0 Replies
5. Web Development
REF:
https://github.com/mattmezza/vue-beautiful-chat
$ git clone https://github.com/mattmezza/vue-beautiful-chat.git
Cloning into 'vue-beautiful-chat'...
remote: Enumerating objects: 534, done.
remote: Total 534 (delta 0), reused 0 (delta 0), pack-reused 534
Receiving objects: 100%... (2 Replies)
Discussion started by: Neo
2 Replies
LEARN ABOUT MOJAVE
jsadebugd
jsadebugd(1) General Commands Manual jsadebugd(1)
NAME
jsadebugd - serviceability agent debug daemon
SYNOPSIS
jsadebugd [pid] [server-id]
jsadebugd executable core [server-id]
DESCRIPTION
jsadebugd attaches to a Java process or core file and acts as a debug server. Remote clients such as jstack, jmap, and jinfo can attach to
the server using Java Remote Method Invocation (RMI). Before starting jsadebugd, rmiregistry must be started with:
rmiregistry -J-Xbootclasspath/p:$JAVA_HOME/lib/sajdi.jar
where $JAVA_HOME is the J2SE SDK installation directory. If rmiregistry was not started, jsadebugd will start an rmiregistry in a standard
(1099) port internally. Debug server may be stopped by sending SIGINT (pressing Ctrl-C) to it.
NOTE - This utility is unsupported and may or may not be available in future versions of the J2SE SDK. jinfo is not currently available on
Windows platforms or on the Linux Itanium platform.
PARAMETERS
pid process id of the process to which the debug server should attach. The process must be a Java process. To get a list of Java
processes running on a machine, jps may be used. At most one instance of the debug server may be attached to a single
process.
executable Java executable from which the core dump was produced.
core core file to which the debug server should attach.
server-id optional unique id, needed if multiple debug servers are started on the same machine. This ID must be used by remote clients
to identify the particular debug server to attach. Within a single machine, this ID must be unique.
SEE ALSO
jinfo(1) jmap(1) jps(1) jstack(1) rmiregistry(1)
13 June 2004 jsadebugd(1)