LUX4 is a powerful and fast communication protocol for Remote Procedure Call (RPC). The library provides both Client and Server classes. C/C++ porting is planned but for the Client side only. LUX4 performances are far ahead of other RPC protocols.
Be the first to post a text review of LUX4. Rate and review a project by clicking thumbs up or thumbs down in the right column.
Just one day after releasing LUX4 as open source, also the SDK (LUX4-SDK) as been released. The LUX4-SDK contains a sample server and some sample client code that can help you explore the features of LUX4 as well as integrating LUX4 in your environment.
LUX4, a super fast communication protocol developed at ERIS4 (http://www.eris4.com), is now Open Source. I'm very excited about this new company strategy of releasing important piece of our technologies to the Open Source community and I can wait to see the community reaction and how will the project get benefits from it. It's all for now. Stay tuned because we have many other interesting enhancements coming up. Regards, Michele Aiello
2.1.2 - First Open Source release. 2.1.1 - Minor bug fixing and log improvements. 2.1.0 - Added a control line at the end of each request. - Auto reconnection in case of IOException. Reconnection parameters configurable via properties file: [ # Reconnection NumberOfRetries=6 RetriesSleepingTime=10000 ] - Changed some method signature to avoid throwing IOException - Mesured Performances of ~700 Events/sec for Single Thread Single Request (on Remote) and ~40KEvents/sec for Single Thread Multi Request (Block Size = 1000). 2.0.8 - Improved logging. 2.0.7 - Improved logging. 2.0.6 - Added SoTimeout settings for server and client socket configurable via properties file: [ # SoTimeouts ServerSocketSoTimeout=1000 ClientSocketSoTimeout=10000 ] This settings are usefull in case of a severe network problem. In that case if you don't have a client socket SoTimeout setted the open connections will remain active forever. - Removed some prints on standard output and added the same prints as info loggin. 2.0.3 - Java 1.3 Compatible. - Removed Asserts, and new exception handling. - Thread.yeald() from properties file. 2.0.0 - Added aggregator invoker and exception handling. 1.8.0a - TDW 1.7.0 - Added support for methods with no arguments. 1.6.0 - Added multi parameters support. Now each method on the server can take more than one parameter as input. public String <method_name> (String one, String two, ..., String n) 1.5.0 - Added multi operations support. Now more than one operation can be defined on the server. The operations must all have the following signature: public String <method_name> (String inputValue) 1.2.0 - Major bug fixing. 1.0.0 - Initial Release. Only one simple operation can be defined on the server: public String handle (String inputValue).
2.1.2 - First Open Source release. 2.1.1 - Minor bug fixing and log improvements. 2.1.0 - Added a control line at the end of each request. - Auto reconnection in case of IOException. Reconnection parameters configurable via properties file: [ # Reconnection NumberOfRetries=6 RetriesSleepingTime=10000 ] - Changed some method signature to avoid throwing IOException - Mesured Performances of ~700 Events/sec for Single Thread Single Request (on Remote) and ~40KEvents/sec for Single Thread Multi Request (Block Size = 1000). 2.0.8 - Improved logging. 2.0.7 - Improved logging. 2.0.6 - Added SoTimeout settings for server and client socket configurable via properties file: [ # SoTimeouts ServerSocketSoTimeout=1000 ClientSocketSoTimeout=10000 ] This settings are usefull in case of a severe network problem. In that case if you don't have a client socket SoTimeout setted the open connections will remain active forever. - Removed some prints on standard output and added the same prints as info loggin. 2.0.3 - Java 1.3 Compatible. - Removed Asserts, and new exception handling. - Thread.yeald() from properties file. 2.0.0 - Added aggregator invoker and exception handling. 1.8.0a - TDW 1.7.0 - Added support for methods with no arguments. 1.6.0 - Added multi parameters support. Now each method on the server can take more than one parameter as input. public String <method_name> (String one, String two, ..., String n) 1.5.0 - Added multi operations support. Now more than one operation can be defined on the server. The operations must all have the following signature: public String <method_name> (String inputValue) 1.2.0 - Major bug fixing. 1.0.0 - Initial Release. Only one simple operation can be defined on the server: public String handle (String inputValue).
Be the first person to add a text review.
Copyright © 2009 Geeknet, Inc. All rights reserved. Terms of Use
Thanks for your rating!
Would you also like to write a review?
Thanks for your review!
Get credit for your review by logging in via OpenID. Click your account provider: