any.proto 5.7 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154
  1. // Protocol Buffers - Google's data interchange format
  2. // Copyright 2008 Google Inc. All rights reserved.
  3. // https://developers.google.com/protocol-buffers/
  4. //
  5. // Redistribution and use in source and binary forms, with or without
  6. // modification, are permitted provided that the following conditions are
  7. // met:
  8. //
  9. // * Redistributions of source code must retain the above copyright
  10. // notice, this list of conditions and the following disclaimer.
  11. // * Redistributions in binary form must reproduce the above
  12. // copyright notice, this list of conditions and the following disclaimer
  13. // in the documentation and/or other materials provided with the
  14. // distribution.
  15. // * Neither the name of Google Inc. nor the names of its
  16. // contributors may be used to endorse or promote products derived from
  17. // this software without specific prior written permission.
  18. //
  19. // THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS
  20. // "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT
  21. // LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR
  22. // A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT
  23. // OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
  24. // SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT
  25. // LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
  26. // DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY
  27. // THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
  28. // (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
  29. // OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
  30. syntax = "proto3";
  31. package google.protobuf;
  32. option csharp_namespace = "Google.Protobuf.WellKnownTypes";
  33. option go_package = "github.com/golang/protobuf/ptypes/any";
  34. option java_package = "com.google.protobuf";
  35. option java_outer_classname = "AnyProto";
  36. option java_multiple_files = true;
  37. option objc_class_prefix = "GPB";
  38. // `Any` contains an arbitrary serialized protocol buffer message along with a
  39. // URL that describes the type of the serialized message.
  40. //
  41. // Protobuf library provides support to pack/unpack Any values in the form
  42. // of utility functions or additional generated methods of the Any type.
  43. //
  44. // Example 1: Pack and unpack a message in C++.
  45. //
  46. // Foo foo = ...;
  47. // Any any;
  48. // any.PackFrom(foo);
  49. // ...
  50. // if (any.UnpackTo(&foo)) {
  51. // ...
  52. // }
  53. //
  54. // Example 2: Pack and unpack a message in Java.
  55. //
  56. // Foo foo = ...;
  57. // Any any = Any.pack(foo);
  58. // ...
  59. // if (any.is(Foo.class)) {
  60. // foo = any.unpack(Foo.class);
  61. // }
  62. //
  63. // Example 3: Pack and unpack a message in Python.
  64. //
  65. // foo = Foo(...)
  66. // any = Any()
  67. // any.Pack(foo)
  68. // ...
  69. // if any.Is(Foo.DESCRIPTOR):
  70. // any.Unpack(foo)
  71. // ...
  72. //
  73. // Example 4: Pack and unpack a message in Go
  74. //
  75. // foo := &pb.Foo{...}
  76. // any, err := ptypes.MarshalAny(foo)
  77. // ...
  78. // foo := &pb.Foo{}
  79. // if err := ptypes.UnmarshalAny(any, foo); err != nil {
  80. // ...
  81. // }
  82. //
  83. // The pack methods provided by protobuf library will by default use
  84. // 'type.googleapis.com/full.type.name' as the type URL and the unpack
  85. // methods only use the fully qualified type name after the last '/'
  86. // in the type URL, for example "foo.bar.com/x/y.z" will yield type
  87. // name "y.z".
  88. //
  89. //
  90. // JSON
  91. // ====
  92. // The JSON representation of an `Any` value uses the regular
  93. // representation of the deserialized, embedded message, with an
  94. // additional field `@type` which contains the type URL. Example:
  95. //
  96. // package google.profile;
  97. // message Person {
  98. // string first_name = 1;
  99. // string last_name = 2;
  100. // }
  101. //
  102. // {
  103. // "@type": "type.googleapis.com/google.profile.Person",
  104. // "firstName": <string>,
  105. // "lastName": <string>
  106. // }
  107. //
  108. // If the embedded message type is well-known and has a custom JSON
  109. // representation, that representation will be embedded adding a field
  110. // `value` which holds the custom JSON in addition to the `@type`
  111. // field. Example (for message [google.protobuf.Duration][]):
  112. //
  113. // {
  114. // "@type": "type.googleapis.com/google.protobuf.Duration",
  115. // "value": "1.212s"
  116. // }
  117. //
  118. message Any {
  119. // A URL/resource name that uniquely identifies the type of the serialized
  120. // protocol buffer message. The last segment of the URL's path must represent
  121. // the fully qualified name of the type (as in
  122. // `path/google.protobuf.Duration`). The name should be in a canonical form
  123. // (e.g., leading "." is not accepted).
  124. //
  125. // In practice, teams usually precompile into the binary all types that they
  126. // expect it to use in the context of Any. However, for URLs which use the
  127. // scheme `http`, `https`, or no scheme, one can optionally set up a type
  128. // server that maps type URLs to message definitions as follows:
  129. //
  130. // * If no scheme is provided, `https` is assumed.
  131. // * An HTTP GET on the URL must yield a [google.protobuf.Type][]
  132. // value in binary format, or produce an error.
  133. // * Applications are allowed to cache lookup results based on the
  134. // URL, or have them precompiled into a binary to avoid any
  135. // lookup. Therefore, binary compatibility needs to be preserved
  136. // on changes to types. (Use versioned type names to manage
  137. // breaking changes.)
  138. //
  139. // Note: this functionality is not currently available in the official
  140. // protobuf release, and it is not used for type URLs beginning with
  141. // type.googleapis.com.
  142. //
  143. // Schemes other than `http`, `https` (or the empty scheme) might be
  144. // used with implementation specific semantics.
  145. //
  146. string type_url = 1;
  147. // Must be a valid serialized protocol buffer of the above specified type.
  148. bytes value = 2;
  149. }