Displaying 1 to 13 from 13 results

Internet Direct - The Indy Project

  •    Delphi

Indy is an open source client/server communications library that supports TCP/UDP/RAW sockets, as well as over 100 higher level protocols including SMTP, POP3, IMAP, NNTP, HTTP, FTP, and many more. Indy is written in Delphi Pascal and is available for Delphi, C++Builder, FreePascal, Delphi.NET, and Kylix.

node-ipc - Inter Process Communication Module for node supporting Unix sockets, TCP, TLS, and UDP

  •    HTML

a nodejs module for local and remote Inter Process Communication with full support for Linux, Mac and Windows. It also supports all forms of socket communication from low level unix and windows sockets to UDP and secure TLS and TCP sockets. This work is licenced via the DBAD Public Licence.

sockets - 🔌 Non-blocking TCP socket layer, with event-driven server and client.

  •    Swift

At the request of the original authors, we ask you to please help us make the community a better place by abiding to this Code of Conduct during your interactions surrounding this project.

sockets - Pure-Swift Sockets: TCP, UDP; Client, Server; Linux, macOS.

  •    Swift

Our goal is to create a safe and empowering environment for anyone who decides to use or contribute to Vapor. Please help us make the community a better place by abiding to this Code of Conduct during your interactions surrounding this project.




goridge - High-performance PHP-to-Golang IPC bridge

  •    PHP

Goridge is high performance PHP-to-Golang codec library which works over native PHP sockets and Golang net/rpc package. The library allows you to call Go service methods from PHP with minimal footprint, structures and []byte support. The MIT License (MIT). Please see LICENSE for more information.

NetSockets

  •    DotNet

NetSockets is a .NET class library that provides easy-to-use, multi-threaded, event-based, client and server network communication.

Indy.Sockets

  •    

Indy.Sockets is an open source socket library that supports clients, servers, TCP, UDP, raw sockets, as well as over 100 higher level protocols such as SMTP, POP3, NNTP, HTTP, and many more. Indy.Sockets is available for C#, C++, Delphi, Visual Basic.NET, any .NET language, an...

Packet Rush Networking Framework

  •    

The Packet Rush Networking Framework (PRNF) provides a client/server networking layer that abstracts away from the underlying communication mechanism such as UDP or TCP.


jsock - JavaScript component for easy JSON handling over sockets or streams

  •    Javascript

JavaScript component for easy JSON handling over sockets or streams. Works in Node.js or the browser.If your JSON objects are too large, you can't simply stringify() it and assume that the full message will be received in one data read on the client. You must use a technique called framing to solve this problem. This is a fancy way of saying that you need to delimit your data so that the receiving end can tell the beginning and the end. jsock does this for you automatically. Now you can build robust communication protocols within Node.js and within the browser.

wait-on - wait-on is a cross-platform command line utility and Node

  •    Javascript

wait-on will wait for period of time for a file to stop growing before triggering availability which is good for monitoring files that are being built. Likewise wait-on will wait for period of time for other resources to remain available before triggering success. For http(s) resources wait-on will check that the requests are returning 2XX (success) to HEAD or GET requests (after following any redirects).

cordova-plugin-chrome-apps-sockets-tcp

  •    Javascript

Plugin is no longer being developed by the MobileChromeApps team. You might want to have a look at KoenLav's fork.

tcpsnitch - TCPSnitch - Tracing the sockets API usage

  •    C

tcpsnitch is a tracing tool designed to investigate the interactions between an application and the TCP/IP stack. tcpsnitch runs the specified command until it exits and intercepts all libc function calls on internet sockets. As a single command may forks multiple processes (and tcpsnitch follows forks), all socket traces belonging to a given process are put together in a directory, named after the traced process. Inside such a directory, socket traces are named based on the order they were opened by the process.





We have large collection of open source products. Follow the tags from Tag Cloud >>


Open source products are scattered around the web. Please provide information about the open source projects you own / you use. Add Projects.