[
https://issues.apache.org/jira/browse/THRIFT-2287?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13865702#comment-13865702
]
Jake Farrell commented on THRIFT-2287:
--------------------------------------
Thanks for the example. as for the formatting question, we are set to use wiki
syntax and can use code blocks by wrapping your code with a starting and ending
\{code\}
example:
{code}
struct FileAction {
string path;
string action;
}
service MirrorService {
//Returns a list of files and the actions taken on them when the mirror is
complete
list<FileAction> mirror(string source, string destination);
}
{code}
> Allow services as parameters
> ----------------------------
>
> Key: THRIFT-2287
> URL: https://issues.apache.org/jira/browse/THRIFT-2287
> Project: Thrift
> Issue Type: Brainstorming
> Reporter: Wayne Rasmuss
> Priority: Minor
>
> What about allowing services as parameters to thrift methods? This would be
> useful for returning interim results, logging and probably other use cases.
> At first I thought, nah that can't work, but I thought about it more and it
> seems maybe it could. Though I know little of Thrift's internals.
> When the service parameter was serialized only its connection information
> would be sent. Additional data may need to be provided to the service (true
> host name etc.) That would be fine with me.
> It seems like both sides should have most of the features they need for this.
> It would probably be a requirement that the service was started, bound etc
> before being passed a a parameter.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
