|Re: [ecf-dev] rest api change?|
In order to address this bug:
I think it's going to be easiest to simply make a change in the org.eclipse.ecf.remoteservice.client.IRemoteResponseDeserializer API:
public Object deserializeResponse(String endpoint, IRemoteCall call, IRemoteCallable callable, Map responseHeaders, String responseBody) throws NotSerializableException;
public Object deserializeResponse(String endpoint, IRemoteCall call, IRemoteCallable callable, Map responseHeaders, byte responseBody) throws NotSerializableException;
(just change the responseBody from type String to type byte).
This change, however, would constitute a breaking API change, meaning that existing clients would need to recompile (at least).
Could those of you interested in this issue please comment on the bug? I would like to address this issue at some time, and now/ECF 3.6 would be a reasonable time, I think.
ecf-dev mailing list
Back to the top