Search Results for "client"

...The inlets-operator brings that same experience to your local Kubernetes cluster by provisioning a VM on the public cloud and running an inlets server process there. Within the cluster, it runs the inlets client as a Deployment, and once the two are connected, it updates the original service with the IP, just like a managed Kubernetes engine.

DBD2 inserts database records from TCP input. It is a companion project to Syslgod2 and an application in its own right. It ships with a backgrounding client for generic use. The client sends whatever information the user puts on the command-line to the back-end daemon via TCP. Upon successful transmission, the client exits. On failure, it backs off and retries until its life-time timer expires. The back-end daemon accepts data from Syslogd2 or its own client and inserts that data (and envelope information) into one or more databases using MySql client library or dbi drivers (also on SourceForge). ...

Ballast is a tool for balancing user load across SSH servers that supports user-specific policies as well as traditional policies based on metrics such as CPU load. It includes a simple client, a lightweight data server, and a data collection agent.

JPPF makes it easy to parallelize computationally intensive tasks and execute them on a Grid.

...If for any reason deployment is failing at a particular stage the process will stop and you can rollback any changes done until then. In case you want to deploy your code or just call your preferred DSC client to apply the configuration locally the Orchestrator can be a handy tool. The operation can be started manually or scheduled, depending on your needs. In terms of audit and trace capabilities, the system is collecting all console output of your shell scripts from all servers and saves the logs centrally for review.

A Java servlet filter which moves session storage out of the java application container, allowing to scale easily by adding more servers, without using a cluster nor changing the code. Session data can be stored into a cookie, memcached, a DB ...

CatBox is designed to help experts and amateurs to configure their Linux/FreeBSD/OSX/Solaris-based system in a simple, yet effective way. CatBox is also based on a client-/server-model.

The app consists of a client, server and web app. orinoco is a remote job scheduler, that was conceived at the coffee house orinco. It is being used a ruby/ruby on rail learning project. features: - start, stop, restart, logging, scheduling, loggin

A PHP Client Library for beanstalkd. BeanStalk allows PHP developers to make use of the beanstalkd in-memory workqueue server (http://xph.us/software/beanstalkd).

The primary goal of the JES is to develop Distributed Configuration Service for client/server,clusters,grids,agent based architectures.

Alternative implementation of Spring framework remoting subsystem that supports different schemes of remote communication between client and server (1-1, 1-many, dynamic services discovering).

An object oriented PHP interface to the Sharedance cache server. Allows you to cache data in the very fast and reliable Sharedance cache server. Features include: Can be distributed across multiple servers, optional redundancy

A Console-based BitTorrent Client with built-in scheduler for handling multiple sessions. It is designed to manage sessions in queue easily without heavy-weight GUI. External module can search for new torrents in trackers and submit it automatically.

A distributed evolution simulation. Features a separate client and server. The client uses OpenGL and OpenAL for visualation and auralization.

A small client/server/node application written in java for distributed computing, or clustering. you write your programs to use this system, you create an object with a meathod to run and send it to the server that assign it a node.

Java package containing architecture to distribute CPU intensive processing tasks across the internet. A generic client will be capable of running any task the server provides it, automatically updating the code it runs.

A Java client for the memcached protocol with a configurable client-side in-process memory cache supporting replacement/eviction strategies (least-recently-used, least-frequently-used, first-in-first-out) designed to provide extremely low-latency lookup.