Hi Mike,
On 3/12/2014 4:28 AM, Mike Wilson wrote:
Ah, no, what I meant was will you a) wait for the R6 spec before
releasing Async support for your Remote Service implementation, or
will you b) wait for both the Async spec and an updated Remote
Services spec before releasing it. I understand that the answer is (a).
This all sounds really good. The only missing piece for me now is
cycle-supporting serialization. You mentioned earlier that your
transport provider is pluggable. If you have some directions on how to
plug in a custom (de)serializer while still keeping the JMS provider
functionality, that would really make my day :-)
I don't often get the ability to publicly make the day of someone that I
don't really know, so [1].
I know this isn't all that you are looking for, and there is more, but I
think the details had better take place on another forum and/or direct
channel.
Scott
[1]
http://git.eclipse.org/c/ecf/org.eclipse.ecf.git/tree/framework/bundles/org.eclipse.ecf.sharedobject/src/org/eclipse/ecf/core/sharedobject/util/ISharedObjectMessageSerializer.java
and/or higher level
http://git.eclipse.org/c/ecf/org.eclipse.ecf.git/tree/providers/bundles/org.eclipse.ecf.provider.remoteservice/src/org/eclipse/ecf/provider/remoteservice/generic/RegistrySharedObject.java
_______________________________________________
OSGi Developer Mail List
[email protected]
https://mail.osgi.org/mailman/listinfo/osgi-dev
