janus | simple way to assume AWS Role | GCP library

V2 signing was introduced in Android 7, so there is no way to escape v1 signing for users on Android 5 and 6.

In Google Play, you can upload multiple APKs in one release, so if you really wanted, you could upload one APK with minSdkVersion=21 with v1 and v2 signatures, and another one with minSdkVersion=24 with v2 signature alone. You will need to make sure that the latter one (24) has a higher versionCode than the former (21) to ensure that they are served as you expect to your users.

The JanusGraph instances for a graph select one instance that maintains an ID pool manager. The JanusGraph reference documentation says the following about optimizing ID allocation:

ID Block Size

Each newly added vertex or edge is assigned a unique id. JanusGraph’s id pool manager acquires ids in blocks for a particular JanusGraph instance. The id block acquisition process is expensive because it needs to guarantee globally unique assignment of blocks. Increasing ids.block-size reduces the number of acquisitions but potentially leaves many ids unassigned and hence wasted. For transactional workloads the default block size is reasonable, but during bulk loading vertices and edges are added much more frequently and in rapid succession. Hence, it is generally advisable to increase the block size by a factor of 10 or more depending on the number of vertices to be added per machine.

Rule of thumb: Set ids.block-size to the number of vertices you expect to add per JanusGraph instance per hour.

Important: All JanusGraph instances MUST be configured with the same value for ids.block-size to ensure proper id allocation. Hence, be careful to shut down all JanusGraph instances prior to changing this value.

ID Acquisition Process

When id blocks are frequently allocated by many JanusGraph instances in parallel, allocation conflicts between instances will inevitably arise and slow down the allocation process. In addition, the increased write load due to bulk loading may further slow down the process to the point where JanusGraph considers it failed and throws an exception. There are three configuration options that can be tuned to avoid this.

1. ids.authority.wait-time configures the time in milliseconds the id pool manager waits for an id block application to be acknowledged by the storage backend. The shorter this time, the more likely it is that an application will fail on a congested storage cluster.

Rule of thumb: Set this to the sum of the 95th percentile read and write times measured on the storage backend cluster under load. Important: This value should be the same across all JanusGraph instances.

1. ids.renew-timeout configures the number of milliseconds JanusGraph’s id pool manager will wait in total while attempting to acquire a new id block before failing.

Rule of thumb: Set this value to be as large feasible to not have to wait too long for unrecoverable failures. The only downside of increasing it is that JanusGraph will try for a long time on an unavailable storage backend cluster.

I would recommend WebRTC. You can pull the feed in a browser, then you don't need to install a client on all those 100 phones.

How are you publishing the audio for WebRTC (to your Janus server)? If possible I would use a WebRTC Agent where you have greater control.

Janus using the streaming plugin provides a really easy way to publish via GStreamer or ffmpeg. You can get greater control over the audio quality that way.

I assume by WebRTC, you are getting user's mic/webcam through navigator.mediaDevices.getUserMedia. I believe the camera light is controlled by the laptop driver and you cannot control it. However, if you do not need video, you can set the constraint parameter:

You can use

Janus Gateway/Server just doesn't support interleaved mode. And with current implementation of RTSP support inside Janus Streaming Plugin (Curl based) it's almost impossible to add such support there.

Make sure you have something like this in your deinit ("screen dismissed completely"?):

If the child component is position absolute then it shouldn’t change the size according to my knowledge. But if the position is relative you can solve the problem by adding min-width and height snd max-width and height in pixels. Other than that I don’t have any solutions.

In my case, this is how I have handled insert DTMF functionality.

a - First filter out audio RTCRtpSender track: