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 "EMF/Net4j 1.0/New and Noteworthy"
< EMF
(New page: EMF 2.4 (available as part of [http://www.eclipse.org/ganymede/ Ganymede] and also separately on the [http://www.eclipse.org/modeling/emf/ EMF] site, contains a number of important and lon...) |
m (→More information) |
||
| (6 intermediate revisions by one other user not shown) | |||
| Line 1: | Line 1: | ||
| − | + | Net4j 1.0 (available as part of [http://www.eclipse.org/ganymede/ Ganymede] and also separately on the [http://www.eclipse.org/modeling/emf/ EMF] site) contains a number of important and long-awaited features, changes, and enhancements. | |
| + | <br> | ||
| + | <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 | ||
| + | <br> | ||
| − | + | ==More information== | |
| − | + | ||
| − | + | ||
| − | + | The Net4j project uses dynamically-generated [http://www.eclipse.org/modeling/emf/news/relnotes.php?project=net4j&version=HEAD release notes], using Bugzilla and CVS data to create accurate lists of bugs closed in each build. This also allows developers and users to see [http://www.eclipse.org/modeling/emf/searchcvs.php?q=project%3A+org.eclipse.emf+days%3A+7 what files were changed] for each bug, by who, and when. For details on how this is done, see [[Search CVS#Parameter_List | Parameter List]]. | |
| − | + | ||
| − | * | + | * [http://www.eclipse.org/modeling/emf/news/relnotes.php?project=net4j&version=HEAD Release Notes] |
| − | + | * [http://www.eclipse.org/modeling/emf/searchcvs.php?q=project%3A+org.eclipse.emf+days%3A+7 Search CVS] | |
| − | + | * [[Search CVS#Parameter_List | Parameter List]] | |
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | * [http://www.eclipse.org/modeling/emf/searchcvs.php?q=project%3A+org.eclipse.emf+days%3A+7 Search CVS] | + | |
| − | + | ||
| − | + | ||
| Line 37: | Line 64: | ||
| − | + | [[Category:Modeling]] [[Category:EMF]] [[Category:Net4j]] | |
| − | + | ||
| − | [[Category: | + | |
Latest revision as of 15:25, 27 June 2008
Net4j 1.0 (available as part of Ganymede and also separately on the EMF site) contains a number of important and long-awaited features, changes, and enhancements.
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
More information
The Net4j project uses dynamically-generated release notes, using Bugzilla and CVS data to create accurate lists of bugs closed in each build. This also allows developers and users to see what files were changed for each bug, by who, and when. For details on how this is done, see Parameter List.