Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "Net4j"
Line 30: | Line 30: | ||
|valign="top"|'''Features'''<br> | |valign="top"|'''Features'''<br> | ||
[[#Core Features|Core Features]]<br> | [[#Core Features|Core Features]]<br> | ||
− | [[# | + | [[#Transports|Transports]]<br> |
[[#Examples|Examples]]<br> | [[#Examples|Examples]]<br> | ||
+ | [[#Utilities|Utilities]]<br> | ||
|} | |} | ||
<br> | <br> | ||
Line 42: | Line 43: | ||
<br> | <br> | ||
− | == | + | ==Transports== |
* NIO-based TCP transport implementation (ITCPConnector, ITCPAcceptor) | * NIO-based TCP transport implementation (ITCPConnector, ITCPAcceptor) | ||
* In-process JVM transport implementation (IJVMConnector, IJVMAcceptor) | * In-process JVM transport implementation (IJVMConnector, IJVMAcceptor) | ||
Line 51: | Line 52: | ||
* Extensible collaborations platform with buddy list, chat, fileshare, ... | * Extensible collaborations platform with buddy list, chat, fileshare, ... | ||
* JMS(TM) provider implementation (experimental but functional) | * 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 | ||
<br> | <br> | ||
Revision as of 05:39, 29 May 2008
Net4j is an extensible client-server communications platform based on OSGi but also executable standalone. You can easily extend the protocol stack with Eclipse plugins that provide new transports or application protocols. Net4j focusses on performance and scalability as well as ease of extension.
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