Download JAR files tagged by real with all dependencies

Leveraging Tencent's 21 years of experience in network and audio/video technologies, Tencent Real-Time Communication (TRTC) offers multi-person audio/video calls and low-latency interactive live streaming solutions. With TRTC, you can quickly develop cost-effective, low-latency, and high-quality interactive audio/video services. Audio/Video Call Solution TRTC provides a client SDK that works across platforms and regions. This solution can be easily used on webpages to enable audio and video call capability for all applications. Low-Latency Interactive Live Streaming Solution TRTC leverages Tencent Cloud's high-quality node resources, industry-leading network and audio/video technologies to helps you build interactive live streaming services with minimal lags and a latency below 1 second, taking live streaming into the era of CDN 2.0.腾讯实时音视频（Tencent Real-Time Communication，TRTC）将腾讯21年来在网络与音视频技术上的深度积累，以多人音视频通话和低延时互动直播两大场景化方案，通过腾讯云服务向开发者开放，致力于帮助开发者快速搭建低成本、低延时、高品质的音视频互动解决方案。

Concourse is a distributed database warehouse for transactions, search, and analytics across time. Developers use Concourse to quickly build mission critical software while also benefiting from real time insight into their most important data. With Concourse, end-to-end data management requires no extra infrastructure, no prior configuration and no additional coding–all of which greatly reduce costs and allow developers to focus on core business problems.

A JNA based library providing access to some low-level Linux subsystems, including :- * UInput. Create virtual devices such as keyboards, mice and touchpads and emit events from them as if they were real. * Evdev. Read events from various devices such as keyboards, mice, touchpads, and all other devices exposed by Linux. * Frame Buffer. Write directly to the Linux framebuffer. Allows graphical user interfaces without X being present. As from version 2.0, this library is now in uk.co.bithatch namespace. Version 2.1 and above support Java 8, and module Java 9 and above.

JARTs are Java-based Asynchronous Real Time sockets. JART uses JNA to build a pure Java TCP/IP stack upon Netmap. It is implemented in imperative style (no TCP state machine) using asynchronous programming with the help of ea-async. JART runs on both Linux (with the proper Netmap kernel module) and FreeBSD with Netmap enabled. FreeBSD 12.1+ has Netmap in the kernel by default so it works "out of the box". While JART has proven fairly robust in limited testing, it is still a work-in-progress and may not be suitable for production use. Pull requests welcome!

Box is an add-on framework for Java EE applications that performs asynchronous gathering of source data with subsequent processing or transformation of that data into output JSON documents and exposing those documents through a web API. Box excels at maintaining existing documents including keeping them up-to-date in real time and deleting them when required. Box supports aggregating data from multiple sources as well as splitting data into multiple documents. How documents are processed is left up to each application. The web api makes the documents available by ID or by harvesting all documents. Harvests can be filtered using facets and documents can be pared down by requesting only needed fields.

An empty artifact that Guava depends on to signal that it is providing ListenableFuture -- but is also available in a second "version" that contains com.google.common.util.concurrent.ListenableFuture class, without any other Guava classes. The idea is: - If users want only ListenableFuture, they depend on listenablefuture-1.0. - If users want all of Guava, they depend on guava, which, as of Guava 27.0, depends on listenablefuture-9999.0-empty-to-avoid-conflict-with-guava. The 9999.0-... version number is enough for some build systems (notably, Gradle) to select that empty artifact over the "real" listenablefuture-1.0 -- avoiding a conflict with the copy of ListenableFuture in guava itself. If users are using an older version of Guava or a build system other than Gradle, they may see class conflicts. If so, they can solve them by manually excluding the listenablefuture artifact or manually forcing their build systems to use 9999.0-....