You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@thrift.apache.org by "James E. King, III (JIRA)" <ji...@apache.org> on 2015/05/08 06:34:00 UTC

[jira] [Commented] (THRIFT-878) Document "core" vs "extra" features

    [ https://issues.apache.org/jira/browse/THRIFT-878?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14533841#comment-14533841 ] 

James E. King, III commented on THRIFT-878:
-------------------------------------------

Might be easier to do this in a Google Spreadsheet collaboratively.  We need to understand things like TSSLSocket support (Perl doesn't have it, for example); TDenseProtocol, TFramedProtocol, TNonBlockingServer.  A matrix would be easy enough to fill in with the language on one axis and the feature on the other.  I would put the feature on the left and language on the top so that features could be grouped together by functional area.

> Document "core" vs "extra" features
> -----------------------------------
>
>                 Key: THRIFT-878
>                 URL: https://issues.apache.org/jira/browse/THRIFT-878
>             Project: Thrift
>          Issue Type: Task
>          Components: Documentation, Website
>            Reporter: Todd Lipcon
>            Assignee: Jake Farrell
>         Attachments: ApacheThriftProfiles.md
>
>
> As discussed in THRIFT-876, we are seeing some divergence between different language implementations as to which features they implement. We need to define which are the "core" Thrift features that users should expect in every language implementation, and then also the "extra" features that some languages implement.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)