One parameter method works fine if we start with proto and define the
services.
But, most of the code is usually evolved, For ex: Existing distributed java
services, who wants to use protobuf, instead of RMI/java-Serialization.
This feature is very useful in doing that.
On Tuesday, August
Can you tell me what's the reason for your decision?
--
You received this message because you are subscribed to the Google Groups
Protocol Buffers group.
To unsubscribe from this group and stop receiving emails from it, send an email
to protobuf+unsubscr...@googlegroups.com.
To post to this
On Tue, Aug 26, 2014 at 2:35 AM, Marvin Somebody h0nswurst...@gmail.com
wrote:
Can you tell me what's the reason for your decision?
We decided against it because such a feature will complicate proto syntax,
API and implementation without bring any true value.
--
You received this message
Hello,
recently I started using protobuf for one of my projects, as I finished
with defining my services I tried to compile but it didn't worked. That was
because I defined my functions like at {2} , I did this because for me as
programmer it is normal that functions can be defined with more
We have discussed this feature request before and the decision is that we
won't support it. To achieve what you need, you can define a new message
type with all the parameters you need as fields and use this message as the
request type.
On Mon, Aug 25, 2014 at 8:30 AM, Marvin Somebody
