Re: [ecf-dev] rest api change?

[Wim Jongman <wim.jongman@xxxxxxxxx>]

Hi Scott,

Would it not be better to deprecate the method and introduce a new interface? 

IRemoteResponseDeserializer2

Best regards,

Wim

On Tue, Jan 29, 2013 at 11:56 PM, Scott Lewis <slewis@xxxxxxxxxxxxx> wrote:

Hi Folks,

In order to address this bug:

https://bugs.eclipse.org/bugs/show_bug.cgi?id=320175

I think it's going to be easiest to simply make a change in the org.eclipse.ecf.remoteservice.client.IRemoteResponseDeserializer API:

from

    public Object deserializeResponse(String endpoint, IRemoteCall call, IRemoteCallable callable, Map responseHeaders, String responseBody) throws NotSerializableException;

to

    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.

thanksinadvance,

Scott







_______________________________________________
ecf-dev mailing list
ecf-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/ecf-dev