1.3.0 released

Added by achristian almost 3 years ago

I totally forgot to post a news about this ... sorry.

SIMON 1.3.0 has been released in 03/2016 ... So, go for it and download the new version ...

1.2.0 ... finally released

Added by achristian over 4 years ago

After about 2 years, there's another SIMON release available. The long-awaited 1.2.0.

You will find it on the Maven Repository as well as the projects download-area.

Feel free to test and report any issue you find.

For our commercial users: If you want to upgrade from 1.1.x, you can get a special offer. Please drop a mail to info[at]

Still alive

Added by achristian about 5 years ago

SIMON is not dead, but seem to reach a stable and feature-rich state.

I cleaned up most of the remaining tickets on the roadmap to version 1.2.0. Right now, there is only one ticket left which needs further investigation.

I will freeze the Roadmap for 1.2.0. So you can now really start testing 1.2.0-SNAPSHOT.

Due to another big personal project ( it will take some time to finish 1.2.0.

SIMON 1.2.0: Only 4 tickets left ..

Added by achristian over 6 years ago

SIMON is on it's way for 1.2.0 release. At the moment, there are only 4 tickets left. I really expect to release 1.2.0 this year. Maybe already in fall. We will see.
One important point for htis release is: SIMON now makes use of the first Java 7 features. Almost 2 years after Java 7 has been released, it was time to upgrade.

SIMON now works on Android

Added by achristian over 6 years ago

SIMON now runs on Android. It required some refactoring for the JVM-only MBean code. First tests showed: It works with Android 4.2.2 + Oracle Java 7 Update 21. But only with classes with primitive instance variables only :(-

Tests showed, that minimum required Android version is 2.3.3 (API10). Further tests will be made to enable transfer of complex objects (classes non-primitive instance variables).

Stay tuned for the stable SIMON 1.2.0 release ...


After some research about transfering complex objects from/to Android, here's my current finding:

As long as you just transfer objects of classes, which are identical on both platforms, there is absolutely no restriction or problem with SIMON and the used serialization mechanism. BUT there are classes on Android which use other byte-stream data than Sun's/Oracle's corresponding Java classes. One example is BigInteger. So, the conclusion is: You're on the safe side if you only transfer objects of your own classes (which are identical on both platforms, or, to be more precise, produce and consume the same byte-stream data).

This is not a limitation of SIMON. This is a general issue with "to Android ported classes", which don't behave identically (w.r.t. serialisation) to corresponding JVM classes.

IANA teil SIMON Port zu ...

Added by achristian over 7 years ago

Heute morgen erreichte mich folgende Email:

Dear Alexander Christian:

Your request has been processed. We have assigned the following
registered port number to SIMON with you as the point of contact:

simon4753tcpSimple Invocation of Methods Over Network (SIMON)

simon-disc4753udpSimple Invocation of Methods Over Network (SIMON) Discovery

The expert review for this request was completed by: Eliot Lear


Konkret heisst das:

SIMON darf den TCP Port 4753 nun offiziell für die RPC Kommunikation nutzen. UDP Port 4753 wird für die Servererkennung genutzt.
Die Änderungen werden in den kommenden Tagen in den SVN trunk eingepflegt.

1 2 3 4 (1-10/33)

Also available in: Atom