STRLCPY/protobuf-decoder

Revision indexing in progress... (symbol navigation in revisions will be accurate after indexed)

Total 1 files

■ ■ ■ ■ ■ ■

README.md

		skipped 19 lines
20	20		Frequently Asked Questions
21	21		--------------------------
22	22
23		-	1. Why can't I edit a decoded proto message?
	23	+	- Why can't I edit a decoded proto message?
24	24
25	25		> Serializing a message requires a proto file descriptor (\*.proto file).
26	26		> Without this proto, we don't know how fields should be serialized.
27	27
28		-	1. What if I have a proto file descriptor?
	28	+	- What if I have a proto file descriptor?
29	29
30	30		> Load it from a Protobuf tab by right-clicking. Messages will be
31	31		> automatically decoded from then on. If you wish to manually
		skipped 4 lines
36	36		> The extension will automatically serialize messages back before
37	37		> they're sent along.
38	38
39		-	1. Can I deserialize protobufs passed as URL or form parameters?
	39	+	- Can I deserialize protobufs passed as URL or form parameters?
40	40
41	41		> Yes, you can. In the 'Protobuf Editor' tab, add a parameter to
42	42		> the table. You can specify additional pre and post processing
		skipped 4 lines
47	47		> You can work around this issue by cycling through requests (anything
48	48		> that'd trigger the editor tab to reload itself)
49	49
	50	+
	51	+	Gotchas
	52	+	-------
	53	+
	54	+	- Since Java doesn't support methods larger than 64k, big proto definitions need
	55	+	to be spit in multiple files. Otherwise, you get the error "Method code too
	56	+	large"
	57	+
	58	+	- proto2 files should always declare syntax = “proto2” in the header instead of
	59	+	leaving it implicit, otherwise it won't work since the default is proto v3
	60	+