diff options
| author |   Petteri Aimonen <jpa@git.mail.kapsi.fi> | 2013-07-06 13:01:21 +0300 |
|---|---|---|
| committer | Petteri Aimonen <jpa@git.mail.kapsi.fi> | 2013-07-06 13:01:21 +0300 |
| commit | 68dd0171bc51e871a522d21a40c35c08de0fb573 (patch) | |
| tree | f1ec0a56f0f1160a7f0f8ca0d011f5d3c0277604 /example/fileproto.proto | |
| parent | a1cec46b3e824292b4ae22fa1f5c4faf9846196c (diff) | |
Switch the example project to use the new .options file
Diffstat (limited to 'example/fileproto.proto')
| -rw-r--r-- | example/fileproto.proto | 14 |
1 files changed, 3 insertions, 11 deletions
diff --git a/example/fileproto.proto b/example/fileproto.proto index e2786b15..3e70c492 100644 --- a/example/fileproto.proto +++ b/example/fileproto.proto @@ -1,22 +1,14 @@ -import "nanopb.proto"; - // This defines protocol for a simple server that lists files. // -// If you come from high-level programming background, the hardcoded -// maximum lengths may disgust you. However, if your microcontroller only -// has a few kB of ram to begin with, setting reasonable limits for -// filenames is ok. -// -// On the other hand, using the callback interface, it is not necessary -// to set a limit on the number of files in the response. +// See also the nanopb-specific options in fileproto.options. message ListFilesRequest { - optional string path = 1 [default = "/", (nanopb).max_size = 128]; + optional string path = 1 [default = "/"]; } message FileInfo { required uint64 inode = 1; - required string name = 2 [(nanopb).max_size = 128]; + required string name = 2; } message ListFilesResponse { |