[gwt-contrib] Re: RPC forward/backward compat

2009-07-24 Thread Matt Mastracci
On 24-Jul-09, at 9:11 PM, BobV wrote: >> Also, will this be supported on methods themselves? For instance, >> can >> I mark a new method parameter as @Optional so that older clients >> don't >> need to provide it? Conversely, could we remove a parameter from a >> method and still support cl

[gwt-contrib] Re: RPC forward/backward compat

2009-07-24 Thread BobV
> Also, will this be supported on methods themselves?  For instance, can > I mark a new method parameter as @Optional so that older clients don't > need to provide it?  Conversely, could we remove a parameter from a > method and still support clients sending data with the old signature? I could g

[gwt-contrib] Re: RPC forward/backward compat

2009-07-24 Thread Matt Mastracci
On 24-Jul-09, at 6:39 PM, BobV wrote: > I have a design wave going on about how to add this to the new RPC > implementation. Here's a cruddy copy-and-paste of the current state > of the document. Bob, this is awesome! Is the plan to land this as part of deRPC, or is this a future feature tha

[gwt-contrib] Re: RPC forward/backward compat

2009-07-24 Thread BobV
> Is the concept of versioning something that belongs in the core GWT > RPC code, or is this something better suited for an external library? I have a design wave going on about how to add this to the new RPC implementation. Here's a cruddy copy-and-paste of the current state of the document.