High-performance TCP & amp; HTTP Communication Framework HP-Socket v4.2.1, high-performance tcp

High-performance TCP & HTTP Communication Framework HP-Socket v4.2.1, high-performance tcp

HP-Socket is a set of common high-performance TCP/UDP/HTTP Communication frameworks, including server components, client components, and Agent components, it is widely used in TCP/UDP/HTTP Communication systems in various application scenarios and provides programming language interfaces such as C/C ++, C #, Delphi, E (easy language), Java, and Python. HP-Socket fully encapsulates the communication layer, and applications do not have to pay attention to any details of the communication layer. HP-Socket provides an API Interface Based on The Event Notification model, it can be easily and efficiently integrated into new and old applications.

In order to allow users to easily and quickly learn and use HP-Socket and quickly master the design ideas and usage methods of the framework, a large number of Demo examples (such: PUSH model examples, PULL model examples, PACK model examples, performance test examples, and other programming language examples ). HP-Socket is currently running on Windows and will be supported across platforms in the future.

HP-Socket v4.2 Development Guide

----------------------------------------------------------------

Versatility

• HP-Socket is only responsible for receiving and sending byte streams and does not participate in Protocol parsing of applications.
• HP-Socket interacts with applications through interfaces and is completely decoupled. Any application that implements the HP-Socket interface specification can seamlessly integrate HP-Socket.

Ease of use

• Ease of use is crucial to all general frameworks. If it is too difficult to use, it is better to write a new one. Therefore, the HP-Socket interface is designed very simple and unified.
• HP-Socket completely encapsulates all the underlying communication details, and applications do not have to or cannot intervene in underlying communication operations. The communication Connection is abstracted as the Connection ID, which is the unique identifier of the Connection provided to the application to process different connections.
• HP-Socket provides PUSH, PULL, PACK, and other receiving models. Applications can flexibly choose to manually, semi-automatically, or fully-automated methods to handle unwrapped packets, the PULL/PACK receiving model reduces the complexity of Packet encapsulation and greatly reduces the probability of errors.

High Performance

• Client components:Based on the Event Select communication model, the communication operation is performed in a separate thread to avoid interference with the main thread or other threads. Each component object manages a Socket connection.
• Server components:Based on the IOCP communication model and combined with the cache pool and Private Heap technologies, it supports ultra-large-scale connections to achieve efficient memory management in high-concurrency scenarios.
• Agent components:For application scenarios such as proxy servers or transit servers, the server itself initiates large-scale connections to other servers as a client. An Agent component object can manage multiple Socket connections at the same time; the Agent and Server components adopt the same technical architecture and can be used as Agent servers or client components of intermediate servers.

Scalability

The application can adjust the performance parameters of HP-Socket according to different capacity requirements, communication scale and resource conditions (for example: number of worker threads, cache pool size, sending mode, and receiving mode) to optimize resource configuration, so as to meet application requirements without excessive waste of resources.

　　 (Project homepage: Click Here, click here)

* ** V4.2.1 update ***

> HTTP Cookie management support

-----------------

> HTTP Sync Client communication component update

-----------------

> Other updates:

-----------------

* ** Update v4.1.3 ***

> WebSocket support:

-----------------

> Added the HTTP Sync Client communication component:

-----------------