[protobuf] Re: PB parsing with empty/reset values
I've been playing with the code this morning and found that the PB is sent, and can be accessed through the doPost method. I was calling doGet from doPost, and attempting to do all relevant actions in there (for consistency), so is there any reason why the inputstream should change due to the method call? -- You received this message because you are subscribed to the Google Groups "Protocol Buffers" group. To post to this group, send email to proto...@googlegroups.com. To unsubscribe from this group, send email to protobuf+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/protobuf?hl=en.
[protobuf] Re: PB parsing with empty/reset values
> It sounds to me like the receiving end didn't actually receive any data -- > you had it parse an empty message, or a garbage message. That's what I thought, it just seems weird that it would work in a separate project. > You should verify that the bytes you got from the serializer and the bytes > you fed to the parser are really the same. For example, compute a checksum > at both ends and print it, then verify manually that they match. As I posted above, I'm not sure how to do this, could you post an example? Thanks for the suggestions. -- You received this message because you are subscribed to the Google Groups "Protocol Buffers" group. To post to this group, send email to proto...@googlegroups.com. To unsubscribe from this group, send email to protobuf+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/protobuf?hl=en.
[protobuf] Re: PB parsing with empty/reset values
On Feb 5, 5:51 pm, Henner Zeller wrote: > Probably unrelated, but if you have binary file content you might > consider using the type 'bytes' instead of 'string'. I considered this but I really need an array of bytes, I'm not sure how this would work with the byte type > This is not really enough information to know what is going on. How do > you transfer the data ? Do you have authentication in place that maybe > fails so that you don't get the data to deserialize ? How does the > receiving side know the length of the data it receives (did you check > that it actually gets the number of bytes you expected to be sent) ? > How do you know that sending it from the android app succeeds ? I have authentication by using command line parameters, I know it works as I have a parent class AbstractServlet which validates requests before calling the requested servlet. The requested servlet runs, so the validation is correct. I'm running eclipse and in debug mode I can check the PB variable, this shows the fields are set correctly. I assume the sending from the app succeeds as the servlet runs on request. I don't know how to check the number of bytes sent or received, would you mind explaining? Thanks for the suggestions. -- You received this message because you are subscribed to the Google Groups "Protocol Buffers" group. To post to this group, send email to proto...@googlegroups.com. To unsubscribe from this group, send email to protobuf+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/protobuf?hl=en.
