Jump to: navigation, search

Difference between revisions of "Net4j"

(Introduction)
(31 intermediate revisions by 2 users not shown)
Line 1: Line 1:
__TOC__
+
__NOTOC__
==Introduction==
+
The Net4j Signalling platform is an extensible client/server communications framework.<br>
 +
Net4j eases the development of fast and maintainable application protocols that are independent<br>
 +
of the physical transport medium. Transport protocols are pluggable and Net4j ships with support<br>
 +
for TCP, HTTP and in-memory transport. The core of Net4j is a fast, asynchronous and non-blocking<br>
 +
buffer multiplexing kernel, based on OSGi but also executable stand-alone.
  
Net4j is an extensible client-server communications platform based on OSGi but also executable stand alone. 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.
+
'''The Net4j project is now integrated into the [[CDO]] project.'''<br>
 +
'''[http://www.eclipse.org/cdo/downloads/ Downloads] and other resources are provided there.'''
 +
<br>
 +
<br>
  
 +
[[Image:Multiplexing.png|600px]]
 +
<br>
 +
 +
==Core Features==
 +
* Extensible signalling framework for '''application protocols''' (IProtocol, SignalProtocol)
 +
* Extensible transport framework for '''physical transports''' (IConnector, IAcceptor)
 +
* '''Multiplexing''' of different application protocols (IChannel)
 +
* Fast, asynchronous and non-blocking '''buffering kernel''' (IBuffer)
 +
<br>
 +
 +
==Transports==
 +
* NIO-based '''TCP''' transport implementation (ITCPConnector, ITCPAcceptor)
 +
* In-process '''JVM''' transport implementation (IJVMConnector, IJVMAcceptor)
 +
* Polling '''HTTP''' transport implementation (IHTTPConnector, IHTTPAcceptor)
 +
<br>
 +
 +
==Examples==
 +
* Extensible collaborations platform with buddy list, chat, fileshare, ...
 +
* JMS(TM) provider implementation (experimental but functional)
 +
<br>
 +
 +
==Utilities==
 +
* Caching and monitoring framework
 +
* Special collections
 +
* Concurrency support
 +
* Wiring framework (managed containers)
 +
* Event framework
 +
* Factory framework
 +
* Generic finite state machine (FSM)
 +
* I/O tools
 +
* Lifecycle framework
 +
* Operations and maintenance framework (OM)
 +
** Platform abstraction (OSGi, Eclipse runtime, stand alone)
 +
** Bundle abstraction
 +
** Logging abstraction
 +
** Tracing abstraction
 +
** Preferences abstraction
 +
** Progress monitoring framework
 +
* Memory sensitivity framework
 +
* Transactional and notifying registries
 +
* Extensible security framework
 +
* Generic transactional operations framework
 +
* Debugging Tools
 +
** Remote tracing (OM extension + Eclipse UI)
 +
** Container view (Eclipse UI)
 +
** Introspector view (Eclipse UI)
 +
* Extensible DB abstraction framework
 +
** Derby DB adapter implementation
 +
** HSQLDB adapter implementation
 +
** MySQL adapter implementation
 +
** PostgreSQL adapter implementation
 +
<br>
  
 
----
 
----
 
Wikis: [[CDO]] | [[Eclipse]] | [http://en.wikipedia.org/wiki/OSGi OSGi] | [http://en.wikipedia.org/wiki/Nio NIO] | [http://en.wikipedia.org/wiki/New_I/O New I/O]
 
Wikis: [[CDO]] | [[Eclipse]] | [http://en.wikipedia.org/wiki/OSGi OSGi] | [http://en.wikipedia.org/wiki/Nio NIO] | [http://en.wikipedia.org/wiki/New_I/O New I/O]
 +
 +
[[Category:Modeling]] [[Category:EMF]] [[Category:Net4j]]

Revision as of 01:37, 30 August 2011

The Net4j Signalling platform is an extensible client/server communications framework.
Net4j eases the development of fast and maintainable application protocols that are independent
of the physical transport medium. Transport protocols are pluggable and Net4j ships with support
for TCP, HTTP and in-memory transport. The core of Net4j is a fast, asynchronous and non-blocking
buffer multiplexing kernel, based on OSGi but also executable stand-alone.

The Net4j project is now integrated into the CDO project.
Downloads and other resources are provided there.

Multiplexing.png

Core Features

  • Extensible signalling framework for application protocols (IProtocol, SignalProtocol)
  • Extensible transport framework for physical transports (IConnector, IAcceptor)
  • Multiplexing of different application protocols (IChannel)
  • Fast, asynchronous and non-blocking buffering kernel (IBuffer)


Transports

  • NIO-based TCP transport implementation (ITCPConnector, ITCPAcceptor)
  • In-process JVM transport implementation (IJVMConnector, IJVMAcceptor)
  • Polling HTTP transport implementation (IHTTPConnector, IHTTPAcceptor)


Examples

  • Extensible collaborations platform with buddy list, chat, fileshare, ...
  • JMS(TM) provider implementation (experimental but functional)


Utilities

  • Caching and monitoring framework
  • Special collections
  • Concurrency support
  • Wiring framework (managed containers)
  • Event framework
  • Factory framework
  • Generic finite state machine (FSM)
  • I/O tools
  • Lifecycle framework
  • Operations and maintenance framework (OM)
    • Platform abstraction (OSGi, Eclipse runtime, stand alone)
    • Bundle abstraction
    • Logging abstraction
    • Tracing abstraction
    • Preferences abstraction
    • Progress monitoring framework
  • Memory sensitivity framework
  • Transactional and notifying registries
  • Extensible security framework
  • Generic transactional operations framework
  • Debugging Tools
    • Remote tracing (OM extension + Eclipse UI)
    • Container view (Eclipse UI)
    • Introspector view (Eclipse UI)
  • Extensible DB abstraction framework
    • Derby DB adapter implementation
    • HSQLDB adapter implementation
    • MySQL adapter implementation
    • PostgreSQL adapter implementation



Wikis: CDO | Eclipse | OSGi | NIO | New I/O