|Re: [ecf-dev] Issue adding custom serialization to ecf provider|
On 7/3/2017 5:50 AM, Peter Hermsdorf wrote:
My inclination is to add/invite you to the ECF organization at github, and create a new repo for this.
* open a bug and create a gerrit change request or should i start something on my github repo and that might be moved to the ECF repo when reuqired?
I think the answer for this depends upon what the scope of the additions will be:ÂÂ e.g. is it a whole new distribution provider (even if based upon existing providers like the generic)...e.g. does it have it's own, new container and Namespace types?ÂÂ If the answer is 'yes' then I would say that you can start something on your repo, and/or we could move it to ECF org at right time, and then...if that's your desire...we can/could move it to eclipse.org.
* I would modify one the existing "hello" or timeservice examples, ok? (i remeber that one of them already had code which uses an ISharedObjectContainer which I also need to register the serializer)
IMHO the timeservice example would be better than the 'hello' examples...as the timeservice examples use OSGi RS/RSA...which is preferred due to the standardization.Â Or, if you have some new example/test code, that would be even better.
Yes.ÂÂ This may already be essentially 'dealt with' by the RSA proxy creation and the generic provider...unless I'm misinterpreting what you are saying.