On 21 May 2015 at 02:45, navin kurle kurlenavi...@gmail.com wrote:
Hi,
How I can remove or delete file using google protobuf?
Well, you need to write your protocol and code that does that. Protobuf
allows you to write the protocol efficiently and platform independently -
but you have to
BTW, you might be interested in reading through
https://developers.google.com/protocol-buffers/docs/encoding. This is
how all the encoding/decoding works.
12 = wire type 2 (0x12 0x7) (length-delimited), field number 2 (0x12 3)
40 = the length (i.e. 64)
the next 64 bytes make up the value for
The first 8 bytes is some kind of header.
the next two bytes are varint tag with field number 1 and interger value =
0
next 6 bytes is also varint tag with field number 2 and value = {five byes}
next 2 bytes says it is a string or byte array with with 6 bytes long. :)
On Tuesday, May 19,
Hey guys,
i want to delete a file from diferent ip (machine)
can some one help me
thanks in advance
--
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
I am trying to understand a protobuf encoded message. the message is given
below, it is apparently a 64 byte long hash value, but I cannot understand
the encoding process
12 01 40 30 37 62 65 37 36 30 34 32 33 35 32 37
33 30 64 64 63 37 38 35 39 39 38 39 34 66 31 31
37 65 30 37 34
I can confirm that this is still a problem with protocol buffers version
2.6.1 and git on Windows set to core.autocrlf=true.
Perhaps this repository should come with a .gitattributes configuration
file with something such as:
# Declare files that will always have LF line endings on checkout.
We are using protobuf as our messaging, and each message, we loop thru the
set fields, and do something with it.
We loop it using
for ( final Map.EntryDescriptors.FieldDescriptor, Object entry :
msg.getAllFields().entrySet()) {
FieldDescriptor field = entry.getKey();
follow up to my previous post... the first four byte is out of my
imagination, but the next 4 bytes indicates 16 that should be the following
message size.
On Tuesday, May 19, 2015 at 11:54:01 PM UTC+2, Jim Muchow wrote:
I sent a question yesterday, but I don't see it as having been
extern KVStr* _init_kv_str(int has_job_id, int job_id,
int has_num_item, int num_item, int n_name)
{
KVStr kv_str = KVSTR__INIT;
...
return kv_str;
}
In the function you are returning local stack variable (kv_str). By the
time pack accesses the message, it probably overwritten.
Hi,
How I can remove or delete file using google protobuf?
Regards,
Navin
On Wednesday, December 10, 2014 at 5:03:38 AM UTC+5:30, Kaustubh Deshmukh
wrote:
Hi Henner,
That worked for me. Thank you for the reply.
On Monday, October 7, 2013 10:59:21 AM UTC-7, Henner Zeller wrote:
On 5
Hm, that 01 byte seems to be extra somehow. Or there are bytes after
this which are missing.
$ perl -ane 'foreach (@F) { print pack C, hex($_) }' | protoc --decode_raw
12 01 40 30 37 62 65 37 36 30 34 32 33 35 32 37
33 30 64 64 63 37 38 35 39 39 38 39 34 66 31 31
37 65 30 37 34 35 36
On Tue, May 19, 2015 at 9:13 PM, Tak Wong yek...@gmail.com wrote:
We are using protobuf as our messaging, and each message, we loop thru the
set fields, and do something with it.
We loop it using
for ( final Map.EntryDescriptors.FieldDescriptor, Object entry :
12 matches
Mail list logo
