Search Results for "p2p over"

Bee is a Swarm client implemented in Go. It’s the basic building block for the Swarm network: a private; decentralized; and self-sustaining network for permissionless publishing and access to your (application) data.There are two versioning schemes used in Bee that you should be aware of. The main Bee version does NOT follow strict Semantic Versioning. Bee hosts different peer-to-peer wire protocol implementations and individual protocol breaking changes would necessitate a bump in the major...

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

Distributed Computing Over P2P Networks(DisCo) is focused to provide a java framework for programmers to develop distributed software application with lesser or no time spent on distributed computing part.

btp2p stands for Bluetooth p2p and it is a collection of java classes for p2p networks over Bluetooth. Useful for CLDC multiplayer games and other applications with extendable design for layered protocols. HuNt is a chatroom midlet based on btp2p.

Hermes is a P2P middleware. It's not a framework, but it's a shell over the existing frameworks. This shell is made in such a fashion that it's possible to the app developer to change the underlying framework without any changes to his app code.

This is an Open Source Project for academic purposes. Coppeer is a P2P framework for developing agent based emergent-behavior application. Over Coppeer we implemented multiple CSCW applications, such as COE and KCE, and Knowledge Management application (

P2P application protocol framework (RFC3080, RFC3081) for connection-oriented, async request/response messages. Allows multiplexing of message streams over one transport connection. Supports binary and textual messages, TLS, SASL/Anonymous, SASL/OTP.

P2P application protocol framework (RFC3080, RFC3081) for connection-oriented, async request/response messages. Allows multiplexing of message streams over one transport connection. Supports binary and textual messages, TLS, SASL/Anonymous, SASL/OTP.

P2P application protocol framework (RFC3080, RFC3081) for connection-oriented, async request/response messages. Allows multiplexing of message streams over one transport connection. Supports binary and textual messages, TLS, and SASL.