Protocol buffer is meant only for serialization & de-serialization. I believe for file attachment you need to have some other implementation such as web services (SAAJ) or http mime attachment. And as Smith said protocol buffer doesn't provide any built in encryption and if you need one, you need to add on top of protocol buffer layer. I had similar conversation before on encryption and may be this is useful for you.
http://groups.google.com/group/protobuf/browse_thread/thread/16a83a5910d62acf Regards, Prakash On Oct 18, 12:12 pm, Christopher Smith <[email protected]> wrote: > On Sun, Oct 17, 2010 at 10:01 PM, nit <[email protected]> wrote: > > > On Oct 14, 4:51 pm, Adam Vartanian <[email protected]> wrote: > > > > I have a file which i need to encrypt and send so can i use > > > > protocol buffer for this buffer? please do reply me. > > > > Protocol buffers don't provide any built-in encryption or anything > > > like that, no, all they provide is a serialization format. You could > > > use protocol buffers to send a file you encrypted via some other > > > method, but I don't think that's what you're asking. > > > > - Adam > > > Hi Adam, > > Thanks a lot for your reply. But I saw in the google code website > > that encoding will be done in Base 128 Varint. So what i understood by > > default was it will be done to all. Is it right?!!!! > > Base 128 Varint is an encoding scheme, not an encryption scheme. > > -- > Chris- Hide quoted text - > > - Show quoted text - -- You received this message because you are subscribed to the Google Groups "Protocol Buffers" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/protobuf?hl=en.
