[
https://issues.apache.org/jira/browse/THRIFT-2287?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Wayne Rasmuss updated THRIFT-2287:
----------------------------------
Description:
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.
was:
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.
> Allow services as parameters
> ----------------------------
>
> Key: THRIFT-2287
> URL: https://issues.apache.org/jira/browse/THRIFT-2287
> Project: Thrift
> Issue Type: Brainstorming
> Reporter: Wayne Rasmuss
>
> 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.4#6159)
