https://sourceforge.net/p/ebus/news/2025-12-15T20:23:27.636000ZRecent posts to news2025-12-15T20:23:27.636000Z2025-12-15T20:23:27.636000ZCharles Rapphttps://sourceforge.net/u/cwrapp/https://sourceforge.netcf3b19600057e6f5522d488c635bb1b7da1931f6

<div class="markdown_content"><p>eBus release 7.6.2</p> <hr/> <p>*** ATTENTION ***</p> <div class="codehilite"><pre><span></span><code> As of release 6.0.0, eBus is now based on Java 11. eBus does <span class="gs">*not*</span> use modules at this time. Therefore include eBus jars in -classpath and not -modulepath. The eBus license also converted from LGPL 2.1 to Apache License 2.0. The reason for the license change is due to Apache License 2.0 being more end-user friendly that LGPL 2.1. </code></pre></div> <hr/> <p>Release 7.6.2 made the following changes:</p> <p>Feature Requests:</p> <p>(No new features.)</p> <p>Bugs:</p> <ul> <li>Ticket 42: Further improvements to AsyncSocket<br/> performance. Includes AsyncSocket unit test re-write to<br/> increase test reliability.</li> </ul> <hr/> <p>There are four download folders:</p> <ul> <li> <p>Library: contains the eBus API jar files.</p> </li> <li> <p>Documentation: contains the eBus Programmer's Manul in PDF and<br/> Javadoc folders in tar, gzipped and zip formats.</p> </li> <li> <p>Source Code: snapshot of eBus maven project files at release<br/> time.</p> </li> <li> <p>Tools: contains the eBus GUI application and configuration file<br/> needed to run the application.</p> </li> </ul></div>

2025-01-03T12:59:24.463000Z2025-01-03T12:59:24.463000ZCharles Rapphttps://sourceforge.net/u/cwrapp/https://sourceforge.net7b3883f69c2070a61742ca24dfa879b478d13fa5

<div class="markdown_content"><p>Release 7.6.0 made the following changes:</p> <p>Feature Requests:</p> <ul> <li> <p>Ticket 40: Added ERequestMonitor role.<br/> Request monitor is able to monitor request, reply, and<br/> cancellation message coversation between a requester and a<br/> <em>local</em> replier. Feed scope is local only and cannot be<br/> changed. Also request monitors do <em>not</em> know whether a<br/> request feed is up or not. This means that messages arrive<br/> without warning.</p> </li> <li> <p>Ticket 41: Change loggers in core module to AsyncLogger.<br/> All core module classes which use logging now use<br/> AsyncLoggerFactory to create a slf4j Logger instance.</p> </li> </ul> <p>Bugs:</p> <p>(No bug fixes.)</p> <p>There are four download folders:</p> <ul> <li> <p>Library: contains the eBus API jar files.</p> </li> <li> <p>Documentation: contains the eBus Programmer's Manul in PDF and<br/> Javadoc folders in tar, gzipped and zip formats.</p> </li> <li> <p>Source Code: snapshot of eBus maven project files at release<br/> time.</p> </li> <li> <p>Tools: contains the eBus GUI application and configuration file<br/> needed to run the application.</p> </li> </ul> <hr/> <p>*** ATTENTION ***</p> <div class="codehilite"><pre><span></span><code> As of release 6.0.0, eBus is now based on Java 11. eBus does <span class="gs">*not*</span> use modules at this time. Therefore include eBus jars in -classpath and not -modulepath. The eBus license also converted from LGPL 2.1 to Apache License 2.0. The reason for the license change is due to Apache License 2.0 being more end-user friendly that LGPL 2.1. </code></pre></div> <hr/></div>

2024-12-17T19:16:01.625000Z2024-12-17T19:16:01.625000ZCharles Rapphttps://sourceforge.net/u/cwrapp/https://sourceforge.net0ef36f6df141fde96a5cdf19abe01c92fa6e9ab3

<div class="markdown_content"><p>eBus 7.5.0 Downloads</p> <hr/> <p>*** ATTENTION ***</p> <div class="codehilite"><pre><span></span><code> As of release 6.0.0, eBus is now based on Java 11. eBus does <span class="gs">*not*</span> use modules at this time. Therefore include eBus jars in -classpath and not -modulepath. The eBus license also converted from LGPL 2.1 to Apache License 2.0. The reason for the license change is due to Apache License 2.0 being more end-user friendly that LGPL 2.1. </code></pre></div> <hr/> <p>Release 7.5.0 made the following changes:</p> <p>Feature Requests:</p> <ul> <li> <p>Ticket 36: Improved net.sf.eBusx.geo API.<br/> Added classes GeoMultiPolygon and GeoCollection, Circle, and Ellipse.<br/> (see <a href="https://gist.github.com/virtualandy/1233401" rel="nofollow">https://gist.github.com/virtualandy/1233401</a>).<br/> Added LineString ring validation required for polygons.<br/> Improved unit test code coverage.</p> </li> <li> <p>Ticket 37: Added TimeLocation to EInterval.<br/> EInterval has begin, end time location data members.<br/> Moved TimeLocation enum from net.sf.eBus.feed.historic.EHistoricSubscribeFeed<br/> to net.sf.eBusx.time.EInterval.</p> </li> <li> <p>Ticket 38: Added bill-of-material module.<br/> Add bill-of-materianl (bom) module to eBus.</p> </li> <li> <p>Ticket 39: Asynchronous slf4j logging.<br/> net.sf.eBus.logging.AsyncLogger encapsulates user slf4j Logger<br/> and performs actual logging on eBus run queue thread.<br/> AsyncLoggerFactory used to create AsyncLogger instance.</p> </li> </ul> <p>Bugs:</p> <p>Ticket 39: General eBus code improvement.<br/> + Use java.lang.Objects where possible when testing possibly<br/> null references and for multi-object hashing.<br/> + Added net.sf.eBusx.monitor.MonitorId unit test.<br/> + Add additional logging where needed for testing purposes.</p> <p>There are four download folders:</p> <ul> <li> <p>Library: contains the eBus API jar files.</p> </li> <li> <p>Documentation: contains the eBus Programmer's Manul in PDF and<br/> Javadoc folders in tar, gzipped and zip formats.</p> </li> <li> <p>Source Code: snapshot of eBus maven project files at release<br/> time.</p> </li> <li> <p>Tools: contains the eBus GUI application and configuration file<br/> needed to run the application.</p> </li> </ul></div>

2024-09-04T15:11:46.983000Z2024-09-04T15:11:46.983000ZCharles Rapphttps://sourceforge.net/u/cwrapp/https://sourceforge.net7df376f0f5b1e539b2c7a086853f81484786d258

<div class="markdown_content"><p>Release 7.4.0 made the following changes:</p> <p>Feature Requests:</p> <ul> <li> <p>Ticket 35: Improved net.sf.eBusx.monitor API.<br/> Existing eBus monitoring package updated to make API easier<br/> to understand and use. Changes are to what notification and<br/> request/reply messages are supported by the monitor<br/> package. It is now possible for a monitoring application to<br/> use an EMultiSubscribeFeed to access all locally and/or<br/> remotely monitored eBus application.</p> <p>The egui application has been updated with a Monitor window<br/> which provides status of the local egui application and<br/> remote eBus applications to which the gui is connected.</p> </li> </ul> <p>Bugs:</p> <p>(No bug fixes.)</p> <p>There are four download folders:</p> <ul> <li> <p>Library: contains the eBus API jar files.</p> </li> <li> <p>Documentation: contains the eBus Programmer's Manul in PDF and<br/> Javadoc folders in tar, gzipped and zip formats.</p> </li> <li> <p>Source Code: snapshot of eBus maven project files at release<br/> time.</p> </li> <li> <p>Tools: contains the eBus GUI application and configuration file<br/> needed to run the application.</p> </li> </ul></div>

2024-06-22T13:55:17.774000Z2024-06-22T13:55:17.774000ZCharles Rapphttps://sourceforge.net/u/cwrapp/https://sourceforge.net13664831ec39c3521e043ababeea150861a892b7

<div class="markdown_content"><p>Release 7.3.0 made the following changes:</p> <p>Feature Requests:</p> <ul> <li> <p>Ticket 33: Switch to org.slf4j logging framework.<br/> Since its inception, eBus used java.util.logging framework<br/> since that was the only framework guaranteed to be available<br/> 20 years ago.</p> <p>With the rise of Maven and Gradle, other logging frameworks<br/> are easily obtained. Given this, eBus API now uses slf4j,<br/> a logging framework which supports any number of underlying<br/> logging frameworks. This means that eBus will use the logging<br/> framework the application chooses.</p> </li> <li> <p>Ticket 34: net.sf.eBus.timer package.<br/> net.sf.eBus.timer.EScheduledTimer works with the eBus<br/> dispatcher framework so that when a scheduled task expires,<br/> that task is placed on the associated eBus objects task queue<br/> and the eBus object is dispatched. That means the eBus object<br/> maintains its effective single threaded nature which eBus<br/> dispatcher guarantees.</p> <p>Using timers like java.util.Timer or<br/> java.util.concurrent.ScheduledExecutorService introduces<br/> threads outside eBus dispatcher and so an eBus object becomes<br/> multi-threaded, requiring thread coordination.</p> </li> </ul> <p>Bugs:</p> <p>(No bug fixes.)</p></div>

2024-01-20T15:34:55.362000Z2024-01-20T15:34:55.362000ZCharles Rapphttps://sourceforge.net/u/cwrapp/https://sourceforge.net6dafecbf88ca2e24016074d4a2d9e844f2beb883

<div class="markdown_content"><p>Release 7.2.0 made the following changes:</p> <p>Feature Requests:</p> <ul> <li> <p>Ticket 32: Add IEMessageStore implementations.<br/> Provide two message store implementations: in-memory and SQL.<br/> In-memory stores a fixed number historic messages using a<br/> ring buffer. These messages are <em>not</em> persisted.</p> <p>The second stores eBus messages in an SQL database. User is<br/> required to provide code which stores, retrieves, and decodes<br/> eBus messages to and from the database.</p> </li> </ul> <p>Bugs:</p> <ul> <li>On-going work cleaning up Sonar code smells.</li> </ul> <p>There are four download folders:</p> <ul> <li> <p>Library: contains the eBus API jar files.</p> </li> <li> <p>Documentation: contains the eBus Programmer's Manul in PDF and<br/> Javadoc folders in tar, gzipped and zip formats.</p> </li> <li> <p>Source Code: snapshot of eBus maven project files at release<br/> time.</p> </li> <li> <p>Tools: contains the eBus GUI application and configuration file<br/> needed to run the application.</p> </li> </ul></div>

2023-12-14T12:48:42.125000Z2023-12-14T12:48:42.125000ZCharles Rapphttps://sourceforge.net/u/cwrapp/https://sourceforge.netaa5684de4fb006e7fec22794c7da3a0afd6a18d9

<div class="markdown_content"><p>Release 7.1.0 made the following changes:</p> <p>Feature Requests:</p> <ul> <li> <p>Ticket 30: Add generic parameter to NotifyCallback.<br/> Currently, NotifyCallback requires method signature to accept<br/> a ENotificationMessage parameter. This means that the<br/> NotifyCallback method has to downcast the message parameter<br/> to the target message type.</p> <p>Adding the generic parameter:</p> <p>public interface NotifyCallback&lt;t extends="" enotificationmessage=""&gt;&lt;/t&gt;</p> <p>to NotifyCallback and using that parameter in:</p> <p>void call(T msg, IESubscribeFeed feed)</p> <p>removes the need for the downcast.</p> <p>This is not available for request and reply messages because<br/> ReplyCallback needs to accept multiple EReplyMessage types<br/> and RequestCallback does not directly receive the<br/> ERequestMessage instance. </p> </li> <li> <p>Ticket 31: Remove lock acquisition from message delivery.<br/> Message routing uses EFeedList.feeds() method to find message<br/> recipients. This method acquires a lock resulting in<br/> inefficient message delivery. This lock is necessary when<br/> adding or removing a feed but not when looking up message<br/> recipients. A solution is to post the feed scope-to-feed list<br/> map to an AtomicReference. This means the feeds() method<br/> calls AtomicReference.get() rather than acquiring a lock<br/> resulting in improved message routing performance. </p> </li> </ul> <p>Bugs:</p> <ul> <li>Ticket 38: InvokeMessageType does not honor @EStringInfo.<br/> Annotation @EStringInfo provides information on String<br/> message fields. This includes the CharSet used to serialize,<br/> de-serialize the String. This information is not honored by<br/> InvokeMessageType when it serializes, de-serializes a String<br/> type. This needs to be corrected.</li> </ul> <p>There are four download folders:</p> <ul> <li> <p>Library: contains the eBus API jar files.</p> </li> <li> <p>Documentation: contains the eBus Programmer's Manul in PDF and<br/> Javadoc folders in tar, gzipped and zip formats.</p> </li> <li> <p>Source Code: snapshot of eBus maven project files at release<br/> time.</p> </li> <li> <p>Tools: contains the eBus GUI application and configuration file<br/> needed to run the application.</p> </li> </ul></div>

2023-10-09T16:29:52.055000Z2023-10-09T16:29:52.055000ZCharles Rapphttps://sourceforge.net/u/cwrapp/https://sourceforge.net340c347491b7818f131eb1421119eebffd170593

<div class="markdown_content"><p>Release 7.0.0 made the following changes:</p> <p>Feature Requests:</p> <ul> <li> <p>Ticket 17: Add reliable UDP connection.<br/> Since UDP packets may either be dropped or arrive<br/> out-of-order, a reliable UDP connection is now in<br/> net.sf.eBus.client package. This implementation uses the<br/> simplest form of reliability: only one application message<br/> may be in flight at a time. Only when the in flight message<br/> is acknowledged may the next message be transmitted.</p> <p>This allows for only a low transmission rate (one message per<br/> millisecond). It is felt this initial implementation is good<br/> enough for most messaging applications.</p> <p>eBus configuration updated to support reliable UDP.</p> </li> <li> <p>Ticket 28: Remove deprecated code.<br/> eBus code marked with @Deprecated was removed. This means<br/> that eBus feeds may only be created and opened using the<br/> feed's builder class.</p> </li> <li> <p>Ticket 29: Use org.jctools queues for task and run queue.<br/> Replace unbounded java.util.concurrent.ConcurrentLinkedQueue<br/> with bounded org.jctools.queue.atomic queues for client task<br/> queue and run queue. Updated eBus configuration to allow<br/> bounded queue capacity to be set, both eBus client task queue<br/> and run queue.</p> </li> </ul> <p>Bugs: (none)</p></div>

2023-08-06T10:42:34.279000Z2023-08-06T10:42:34.279000ZCharles Rapphttps://sourceforge.net/u/cwrapp/https://sourceforge.netdd5e27a54b34a16ba4cf1818dd2c117621df70cb

<div class="markdown_content"><h1 id="reliable-udp-connection">Reliable UDP Connection.</h1> <p>eBus release 7.0.0 will introduce a simple reliable UDP connection guaranteeing UDP packets arrive in order and no missing packets. More about this later.</p> <h1 id="deprecated-method-removal">Deprecated method removal.</h1> <p>Release 7.0.0 will also be dropping the deprecated feed open methods and related methods and data members. This means that feeds may only be created using the associated builder. If still using feed open methods, then moving to eBus release 7.0.0 will require code changes.</p></div>

2023-07-29T11:28:24.710000Z2023-07-29T11:28:24.710000ZCharles Rapphttps://sourceforge.net/u/cwrapp/https://sourceforge.netb6db51f59b347f81a7e7934e38067fdee56ed646

<div class="markdown_content"><h1 id="ebus-660-going-mobile">eBus 6.6.0: Going Mobile</h1> <p>Release 6.6.0 made the following changes:</p> <p>Feature Requests:</p> <ul> <li>Ticket 25: Make eBus API Android-compatible<br/> This required removing use of <code>java.lang.management</code> package. Added <code>net.sf.eBus.util.ERuntime</code> class which provides static method isAndroid which returns true if running on Android Runtime (ART). eBus API v. 6.6.0 is verified as being Android-compatible.</li> <li>Ticket 26: Make StatusReporter a functional interface.<br/> <code>net.sf.eBus.util.logging.StatusReporter</code> is now marked with <code>@FunctionalInterface</code> allowing compatible methods to be used for status reporting.</li> <li>Ticket 27: Use <code>SocketAddress</code> for binding.<br/> Server and client TCP and UDP sockets (both secure and cleartext) may now be bound to a SocketAddress rather than just a port. Previous methods which only bound to a port is still supported but will use the wildcard address.</li> </ul> <p>Bugs:</p> <ul> <li> <p>Ticket 36: Correct TLS handshake race condition.<br/> A race condition exists TLS handshake between initiating client and accepting service. The initiating TCP socket may be told that the the handshake status is FINISHED but the accepted TCP socket is still processing the final handshake message. The result is that the initiating client sends an eBus logon message before the acceptor is ready to receive it and so the logon message is ignored.</p> <p>Solution is for initiating client to wait for acceptor to complete its handshake before sending eBus logon message.</p> </li> <li> <p>Ticket 37: Correct <code>ERemoteApp</code> message key map.<br/> <code>ERemoteApp</code> maps message key to the remote advertised or subscribed feed. Because an advertisement and subscription can both reference the same message key, <code>ERemoteApp</code> can think there is a redundant advertisement or subscription if it receives both an advertisement and subscription for the same message key.</p> <p>The solution is to use <code>MultiKey2&lt;(Ad, Subscription), EMessageKey&gt;</code>. This allows both a remote advertisement and subscription to use the same message key.</p> </li> </ul> <p>There are four download folders:</p> <ul> <li> <p>Library: contains the eBus API jar files.</p> </li> <li> <p>Documentation: contains the eBus Programmer's Manul in PDF and<br/> Javadoc folders in tar, gzipped and zip formats.</p> </li> <li> <p>Source Code: snapshot of eBus maven project files at release<br/> time.</p> </li> <li> <p>Tools: contains the eBus GUI application and configuration file<br/> needed to run the application.</p> </li> </ul></div>