HaRMIClient raises exception in invoking call proxy #49
Comments
fritzprix
added a commit
that referenced
this issue
Nov 6, 2018
Prior to this change, the implementation for service discovery should handle listed below.. 1. retrieve service information from service advertiser 2. convert it to service proxy that was too complicated to be applied widely used service discovery technology (like mdns ..) 1.separate service info converting functionality from the discovery 2.remove ad-hoc tick timer for service information retrival which is not well compatible to another service discovery implementation close #49, #48, #37, #39
fritzprix
added a commit
that referenced
this issue
Nov 6, 2018
* Add support for Primitive type (e.g. int, double, etc.) in serialization & deserialization * simplify implementation for service discovery and improve genericity Prior to this change, the implementation for service discovery should handle listed below.. 1. retrieve service information from service advertiser 2. convert it to service proxy that was too complicated to be applied widely used service discovery technology (like mdns ..) 1.separate service info converting functionality from the discovery 2.remove ad-hoc tick timer for service information retrival which is not well compatible to another service discovery implementation close #49, #48, #37, #39 * change method name for service discovery
fritzprix
added a commit
that referenced
this issue
Nov 6, 2018
* Add support for Primitive type (e.g. int, double, etc.) in serialization & deserialization * simplify implementation for service discovery and improve genericity Prior to this change, the implementation for service discovery should handle listed below.. 1. retrieve service information from service advertiser 2. convert it to service proxy that was too complicated to be applied widely used service discovery technology (like mdns ..) 1.separate service info converting functionality from the discovery 2.remove ad-hoc tick timer for service information retrival which is not well compatible to another service discovery implementation close #49, #48, #37, #39 * change method name for service discovery * update README
fritzprix
added a commit
that referenced
this issue
Nov 6, 2018
* solve random request drop there was random request drop happened in concurrent method invocation request and response has 1:1 relationship with simple incremental unique value. however, increase of the value was not atomic, which means two different requests can have the same value. so one request remains not notified by response while the other is notified normally. * change field name * bug fix (reflect API update) * 0.0.5 snapshot primitive sedes (#54) * Add support for Primitive type (e.g. int, double, etc.) in serialization & deserialization * simplify implementation for service discovery and improve genericity Prior to this change, the implementation for service discovery should handle listed below.. 1. retrieve service information from service advertiser 2. convert it to service proxy that was too complicated to be applied widely used service discovery technology (like mdns ..) 1.separate service info converting functionality from the discovery 2.remove ad-hoc tick timer for service information retrival which is not well compatible to another service discovery implementation close #49, #48, #37, #39 * change method name for service discovery * 0.0.5 snapshot primitive sedes (#55) * Add support for Primitive type (e.g. int, double, etc.) in serialization & deserialization * simplify implementation for service discovery and improve genericity Prior to this change, the implementation for service discovery should handle listed below.. 1. retrieve service information from service advertiser 2. convert it to service proxy that was too complicated to be applied widely used service discovery technology (like mdns ..) 1.separate service info converting functionality from the discovery 2.remove ad-hoc tick timer for service information retrival which is not well compatible to another service discovery implementation close #49, #48, #37, #39 * change method name for service discovery * update README
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
method invoke with null argument was equivalent to invoke with no argument in Java8 (no problem with no-arg method)method invoke with null argument for no-arg method raise IllegalArgumentException in Java7originally method invocation has been directly performed by calling RMIClient::invoke method and it was changed to calling call proxy of RMIClient later. however, the invocation has not reflected the change
The text was updated successfully, but these errors were encountered: