You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@thrift.apache.org by "Bryan Duxbury (JIRA)" <ji...@apache.org> on 2009/02/07 02:10:59 UTC

[jira] Resolved: (THRIFT-303) Changes to __isset interface

     [ https://issues.apache.org/jira/browse/THRIFT-303?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Bryan Duxbury resolved THRIFT-303.
----------------------------------

    Resolution: Fixed

I just committed this.

> Changes to __isset interface
> ----------------------------
>
>                 Key: THRIFT-303
>                 URL: https://issues.apache.org/jira/browse/THRIFT-303
>             Project: Thrift
>          Issue Type: Improvement
>          Components: Compiler (Java), Library (Java)
>            Reporter: Bryan Duxbury
>            Assignee: Bryan Duxbury
>            Priority: Minor
>             Fix For: 0.1
>
>         Attachments: thrift-303.patch
>
>
> I think that it would make a lot of sense for us to redefine the __isset interface of Java generated structs. With the changes in THRIFT-297, all TBase objects will now have the isSet generic method as well as isMyFieldSet per-field isset checkers. This gives the same kind of information as direct access to __isset as the public field does, but has the added advantage of hiding the information behind a method-based interface, freeing us to do things like THRIFT-115 and THRIFT-116 without breaking future clients. 
> Especially with the future proposition of making a release, now would be a great time to improve this interface.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.