Search Results for "process communication"

...It takes only couple lines to access, whether plug-ins or main programs. RePlugin owns stable plug-in management solution which supports installation, upgrade, uninstallation and version management. Process communication, protocol versions and security check are also included. RePlugin possesses hundreds of millions users from 360 MobileSafe.

A Java middleware API supporting broker-less, type+topic-based publish/subscribe and request/reply messaging for both intra- and inter-application, object-level communication. Broker-less: messages are transmitted directly between eBus applications. There is no message broker (i.e. server) in between. Type+topic addressing: eBus clients subscribe to a message class (type) and message topic, providing stronger typing than just topic-based subscriptions. Object-level communication: eBus delivers messages directly to client objects, not to a client process.

...SSL/TLS security for network communication, X.509 certificates for peer to peer mutual authentication.

Ribbon is a Inter Process Communication (remote procedure calls) library with built in software load balancers. The primary usage model involves REST calls with various serialization scheme support. Ribbon comprises of multiple components some of which are used in production internally and some of which were replaced by non-OSS solutions over time. This is because Netflix started moving into a more componentized architecture for RPC with a focus on single-responsibility modules. ...

...Support register route meta dynamic. Forward from external URLs to internal pages, and parsing parameters. Jump and decoupling between multi-module. Intercept jump process, handle login, statistics and other logic. Cross-module communication, decouple components by IoC.

...The multi-threading part aims to show how to avoid blocking methods by putting them in separate thread, therefor, the ExecutorService was not used. Two Runnable interfaces are available in the server and the client to show how the dialog is managed. The Socket part aims to show how simple communication using TCP/IP are quite simple. The system shows how to exchange and process String over network. This is not sufficient when talking about large applications, but, let's not forget that HTTP uses Strings. The project contains both the Server and the Client. The main method in the Main class does nothing. You must launch the Server (ServerMain) and several instances (or just one) of the Client (ClientMain). ...

Nepenthes is a sub-middleware for iOS & macOS App development,which sets the standards for java back-end and Objective-C front-end development.Nepenthes back-end is based on Apache Tomcat or other J2EE compatible middleware by extends Nepenthes library.Nepenthes front-end is mapping to back-end with the support of Nepenthes framework. Nepenthes simplifies development process and shortens development lifecycle,it ensures the communication layer safe and solid,let your team focus only on business logic. Based on Nepenthes,your organization can develop very complicated enterprise Apps rapidly,reduce back-end and front-end teams employees nearly to half. Reduce the communication errors in the development debugging,raise project development speed dramatically. ...

SEvents is a System of Event programming with random factor designed to accept a script file and execute it with using extra modules. One module - one object, which relate on changing of some variables.

The Melting Pot - a Java framework for component-based software engineering in Java; inter-component communication implemented via synchronous or asynchronous calls or messaging; overall application can be a single process or fully distributed.

jiipco! (Java Internal Interprocess Communication) is a library for event driven process communication, specially suited for frontend GUIs development. With this library, command line oriented utilities can be treated as asynchronous event generators.

GENESIS is an OS environment that supports the cooperation and communication between software engineers belonging to distributed software development teams. It includes resources,projects and artefacts management,workflow engine, process definition.