Search Results for "node"

...Currently the solution of choice is to use a light client or remote client on mobile devices. While this may work for mobile phones, most IoT devices are unable to run light clients. Connecting an IoT device to a remote node enables even low-performance IoT devices to be connected to blockchain. However, by using distinct remote nodes, the advantages of a decentralized network are undermined introducing a single point of failure. Also, it is unsecure because the client is not able to verify the results by itself. The same applies for mobile apps or web pages.

...The design focuses on simplicity, providing a minimal and clear API for producers to enqueue jobs (messages) and consumers to process them, while handling replication, failure and re-queueing internally. Disque supports multi-master clusters where any node can serve producers and consumers, and messages are asynchronously replicated to a configurable number of nodes to ensure availability even in the face of failures. It offers both at-least-once and at-most-once delivery semantics depending on per-message configuration, and retries or re-queueing of un-acknowledged jobs are built in. ...

OpenGGSN is a Gateway GPRS Support Node (GGSN). It is used by mobile operators as the interface between the Internet and the rest of the mobile network infrastructure. The project also developed an SGSN emulator suitable GPRS core network testing. OpenGGSN is maintained within the Osmocom (open source mobile communications) project. Source code repository is at http://cgit.osmocom.org/openggsn/ Mailing list is at https://lists.osmocom.org/mailman/listinfo/osmocom-net-gprs Wiki is at https://osmocom.org/projects/openggsn/wiki

When you synchronize 2 file repositories with rsync, then you want to use fsize to show you if both sides show up with the same amount of files and with the same file sizes. Using du always counts files and directories (option -sb), which can result in different sizes. A directory node may use 12 KB on the rsync source and 16 KB on the rsync destination.

...The goal is to handle high availability by storing copy of the same file on several nodes. HADOS provides RESTFUL APIs to easily store, check or retrieve files. Using the powerful cluster APIs you can retrieve the files whatever the node that hosts it. To avoid any single point of failure, it is possible to apply a request to any node of the cluster, there is no master node.

...It uses following protocol stack: MAP (moForwardSM and mtForwardSM) TCAP (Begin with Invoke + End with ReturnResultLast) SUA (SCCP User Adaptation): ASP UP/ASP ACTIVE + ACK's and CLDT messages only SCTP (Linux Kernel - SCTP implementation) IP Current implementation is tested in SAMK NGN [http://www.samk.fi/ngn] laboratory's 3G mobile network (real Nokia MSC/VLR network hardware with UTRAN RLC and node-B). Thesis URL: http://urn.fi/URN:NBN:fi:amk-2013052210011

A Load Balancer for a VoIP software on a Mobile Node device that choose among three net interfaces to send packages to an other Load Balancer on a Fixed Node. The LB's aim is to lose the lowest number of packages, choosing the best net interface.

The IRLP-Repeater script allows you to turn an IRLP node into a repeater contoller with the use of just two radios, a duplexer and antenna.

The firmware for a MSP430 based full duplex terminal node controller supporting connectionless AX.25.

IRLP-LCD is a client for LCDproc to display the status of an IRLP node. This program is written in C, and runs directly on the IRLP node. This program should run on any Redhat 9 or Fedora node. Requires LCDproc on the same or another system.

Features include: authentication, channel control, a full-featured Memo system, a Seen system, logging capabilities, a help system, the ability to act as a file sharing node and the ability to share data and perform functions together with other bots.

a udp based peer to peer network project with routing and a self organizing quarum based network arch.

A plugin for Gaim that replaces [square bracketed text] with a link to the corresponding Everything2 node.