thrift-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Noam Wolf <noam.w...@gmail.com>
Subject Re: Bad type in structure
Date Mon, 22 Feb 2010 18:54:30 GMT
it was my understanding that the id's were a unique, sequential, index... i
guess it makes sense that they don't need to be sequential but if I don't
have control over the server this might not be a good solution.

On Mon, Feb 22, 2010 at 6:41 PM, Ted Dunning <ted.dunning@gmail.com> wrote:

> It might help if you changed the id number on the argument when you change
> the semantics.  That will let your applications fail in cases like this.
>
> On Mon, Feb 22, 2010 at 10:17 AM, Noam Wolf <noam.wolf@gmail.com> wrote:
>
> > Basically my service call changed from
> >
> > doSomething(1: String request)
> >
> > to
> >
> > doSomething(1: Request request)
> >
> > So when I was calling doSomething("foo") i was seeing that error because
> > the
> > type i was passing to the service was not the correct type...
> >
> > hopefully this will help someone some day...
> >
>
>
>
> --
> Ted Dunning, CTO
> DeepDyve
>



-- 
Best Regards,
Noam Wolf

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message