npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

nextrtc-js-client

v1.0.8

Published

JS Client to NextRTC signaling server

Downloads

78

Readme

NextRTC JavaScript client

NextRTC js client constructor requires:

  • wsURL which should points to your endpoint {ws/wss}://{host}:{port}/{applicationName}/{endpointGivenInAnnotation} endpointGivenInAnnotation e.g. – @ServerEndpoint(value = “/signaling” …)
  • mediaConfig are passed straight to adapter, so more information about parametres you can find in webrtc/adapter documentation.
  • peerConfig are also described in webrtc/adapter project.

Example is shown below and it’s also available in nextrtc-sample-webapp

new NextRTC({
    wsURL : 'wss://examples.nextrtc.org/videochat/signaling',
    mediaConfig : {
        video : true,
        audio : true,
    },
    peerConfig : {
        'iceServers' : [ {
            url : "stun:stun.l.google.com:19302"
        }]
    }
}/*, optional DEBUG mode /true or false/*/);

How to use nextrtc-js-client on static page?

When page will be fully loaded you should create nextrtc object. If you don’t know when your page is fully loaded you can use override method NextRTC.onReady (this way of use is presented in example).

When you create NextRTC object you have to provide function which will be called when event happens. To register function you have to call method on() as presented in snipped:

var nextRTC = new NextRTC({
    ...
});

nextRTC.on('{eventName}', function(event:Event){
    
});

There are two signals which are providing other second parameter type. Those signals are: localStream and remoteStream, when you are handling local audio/video stream and incoming audio/video stream you can simply attach stream to valid element (without additional action like resolving stream by description provided in event).

nextRTC.on('{localStream|remoteStream}', function({stream: Stream, member: memberId}){

});

How to send / handle custom signals?

On the js side you have to write two methods. One for sending new signal

NextRTC.prototype.upperCase = function upperCase(content, custom) {
    this.channel.send({signal: 'upperCase', content: 'content', custom: custom});
}; 

second one which will react on the response:

nextRTC.on('upperCase', content => {
// here you should handle the response
});

Then you will be able to use structure like this to post your custom signal:

nexrtc.upperCase('lowerCase');

Model

Event structure and available events are presented here

Event is serialized java version of message.