Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "Net4j"
(New page: Net4j is an extensible client-server system. You can easily extend the protocol stack with Eclipse plugins that provide new transport or application protocols. Net4j's focus on performance...) |
|||
Line 1: | Line 1: | ||
Net4j is an extensible client-server system. You can easily extend the protocol stack with Eclipse plugins that provide new transport or application protocols. Net4j's focus on performance and scalability is featured by non-blocking I/O, zero-copy signals and multiplexed binary protocols. Net4j was originally developed to support the [[CDO]] technology for distributed shared and persistent EMF models but can also multiplex your own user-supplied application protocols through the same socket connection. | Net4j is an extensible client-server system. You can easily extend the protocol stack with Eclipse plugins that provide new transport or application protocols. Net4j's focus on performance and scalability is featured by non-blocking I/O, zero-copy signals and multiplexed binary protocols. Net4j was originally developed to support the [[CDO]] technology for distributed shared and persistent EMF models but can also multiplex your own user-supplied application protocols through the same socket connection. | ||
+ | |||
+ | ---- | ||
+ | Wikis: [[CDO]] | [[Eclipse]] | [http://en.wikipedia.org/wiki/Nio NIO] |
Revision as of 17:22, 18 October 2007
Net4j is an extensible client-server system. You can easily extend the protocol stack with Eclipse plugins that provide new transport or application protocols. Net4j's focus on performance and scalability is featured by non-blocking I/O, zero-copy signals and multiplexed binary protocols. Net4j was originally developed to support the CDO technology for distributed shared and persistent EMF models but can also multiplex your own user-supplied application protocols through the same socket connection.