It looks like below,
client's messages are organised as below and sending them in following
order.
<---TP header + CS header + (PB messages)<---
TP header consits with 6fields - 30bytes
CS header with 2fields - 4bytes
PB message
message ReplyData {
enum ErrorCodeType {
UNSPECIFIED = 0;
NOT_STARTED = 1;
SLEEPING = 4;
DRIVING = 5;
CANCELING = 6;
}
optional uint32 command_ref = 1
optional string error = 2;
optional String ErrorCodeType = 3 [default = UNSPECIFIED];
}
On Tuesday, February 26, 2013 3:24:29 PM UTC+8, Pradeep Rathnayaka wrote:
>
> I newbie to protocol buffers, I am currently working on a new java
> client/server standalone application. The system transfers messages
> between client and server where the process should be happened over a
> restricted network(WLAN). I chosen protocol buffer messages technology to
> transfer data efficiently in fast manner. In my case the client's messages
> consist with several header portions and body(data) itself.
> I have designed this to serialize client's messages data(body) into
> protocol buffer messages and then messages will be sending together with
> header portions to the server. is this good design for me?
> Thanks.
>
--
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 [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/protobuf?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
