{"id":29376519,"url":"https://github.com/twitter/serial","last_synced_at":"2025-07-09T22:43:22.892Z","repository":{"id":23188255,"uuid":"97140654","full_name":"twitter/Serial","owner":"twitter","description":"Light-weight, fast framework for object serialization in Java, with Android support.","archived":false,"fork":false,"pushed_at":"2023-04-10T11:21:25.000Z","size":306,"stargazers_count":991,"open_issues_count":9,"forks_count":103,"subscribers_count":41,"default_branch":"master","last_synced_at":"2024-05-09T19:35:01.581Z","etag":null,"topics":[],"latest_commit_sha":null,"homepage":null,"language":"Java","has_issues":true,"has_wiki":null,"has_pages":null,"mirror_url":null,"source_name":null,"license":"apache-2.0","status":null,"scm":"git","pull_requests_enabled":true,"icon_url":"https://github.com/twitter.png","metadata":{"files":{"readme":"README-CHINESE.rst","changelog":null,"contributing":null,"funding":null,"license":"LICENSE","code_of_conduct":null,"threat_model":null,"audit":null,"citation":null,"codeowners":null,"security":null,"support":null,"governance":null}},"created_at":"2017-07-13T15:52:13.000Z","updated_at":"2024-04-23T11:55:43.000Z","dependencies_parsed_at":"2022-07-11T20:02:41.887Z","dependency_job_id":"cfaba12c-aabe-4741-92f5-9f56a87bad4e","html_url":"https://github.com/twitter/Serial","commit_stats":null,"previous_names":[],"tags_count":0,"template":false,"template_full_name":null,"purl":"pkg:github/twitter/Serial","repository_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/twitter%2FSerial","tags_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/twitter%2FSerial/tags","releases_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/twitter%2FSerial/releases","manifests_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/twitter%2FSerial/manifests","owner_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners/twitter","download_url":"https://codeload.github.com/twitter/Serial/tar.gz/refs/heads/master","sbom_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/twitter%2FSerial/sbom","host":{"name":"GitHub","url":"https://github.com","kind":"github","repositories_count":264504616,"owners_count":23618831,"icon_url":"https://github.com/github.png","version":null,"created_at":"2022-05-30T11:31:42.601Z","updated_at":"2022-07-04T15:15:14.044Z","host_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub","repositories_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories","repository_names_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repository_names","owners_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners"}},"keywords":[],"created_at":"2025-07-09T22:43:22.278Z","updated_at":"2025-07-09T22:43:22.884Z","avatar_url":"https://github.com/twitter.png","language":"Java","funding_links":[],"categories":[],"sub_categories":[],"readme":"|badge1| |badge2| |badge3|\n\n.. |badge1| image:: https://travis-ci.org/twitter/Serial.svg?branch=master\n    :target: https://travis-ci.org/twitter/Serial\n\n.. |badge2| image:: https://img.shields.io/maven-central/v/com.twitter.serial/serial.svg\n    :target: https://repo1.maven.org/maven2/com/twitter/serial/serial/\n\n.. |badge3| image:: https://img.shields.io/badge/license-Apache%20License%202.0-blue.svg?style=flat\n    :target: https://raw.githubusercontent.com/twitter/Serial/master/LICENSE.txt\n\nTwitter Serial\n==============\n\nEnglish Doc : https://github.com/twitter/Serial/blob/master/README.rst\n\n依赖\n--------\n从Maven Central上下载最新的依赖：\n\n.. code-block:: java\n\n  repositories {\n    mavenCentral()\n  }\n\n  dependencies {\n    implementation 'com.twitter.serial:serial:0.1.6'\n  }\n \n简介\n--------\n\nSerial是Twitter出品的高性能序列化方案，它力求帮助开发者实现高性能和高可控的序列化过程。\n\n这个序列化框架提供了一个名叫Serializers的序列化器，开发者可以通过它来明确地定义对象的序列化过程。\n\nSerial方案的主要优点如下：\n\n- 相比起传统的反射序列化方案更加高效（没有使用反射）\n\n  - 性能相比传统方案提升了3倍 （序列化的速度提升了5倍，反序列化提升了2.5倍）\n  - 序列化生成的数据量（byte[]）大约是之前的1/5\n\n- 开发者对于序列化过程的控制较强，可定义哪些object、field需要被序列化\n- 有很强的debug能力，可以调试序列化的过程（详见：`调试`_）\n\n**译者注：**\n\nSerializer是本库中的关键类，这个类提供了序列化和反序列化的能力，序列化的定义和流程都是通过它来实现的。\n\n基础结构\n---------------\n\n将一个对象序列化为byte[]：\n\n.. code-block:: java\n\n  final Serial serial = new ByteBufferSerial();\n  final byte[] serializedData = serial.toByteArray(object, ExampleObject.SERIALIZER)\n\n将对象从byte[]反序列化为object：\n\n.. code-block:: java\n\n  final ExampleObject object = serial.fromByteArray(serializedData, ExampleObject.SERIALIZER)\n\n**译者注：**\n\n目前库中默认提供的序列化实现类是ByteBufferSerial，它的产物是byte[]。使用者也可以自行更换实现类，不用拘泥于byte[]。\n\n\n定义Serializer\n--------------------\n\n- 于之前的实现Serializable接口不同，这里需要给每个被序列化的对象单独定义一个Serializer\n- Serializers中需要给每个field明确的定义write和read操作，对于有继承关系的序列化类，需要被递归的进行定义\n- Serializers已经为使用者处理了空对象问题，就像read/writeString一样，记住不要使用原始的方法\n- Serializers是无状态的，所以我们可以将其写为object的内部类，并通过 ``SERIALIZER`` 作为名称来访问它\n\n对于大多数类，你可以建立一个继承自 ``ObjectSerializer`` 的子类，然后实现 ``serializeObject`` 方法和 ``deserializeObject`` 方法：\n\n.. code-block:: java\n\n  public static class ExampleObject {\n\n      public static final ObjectSerializer\u003cExampleObject\u003e SERIALIZER = new ExampleObjectSerializer();\n\n      public final int num;\n      public final SubObject obj;\n\n      public ExampleObject(int num, @NotNull SubObject obj) {\n          this.num = num;\n          this.obj = obj;\n      }\n\n      ...\n\n      private static final class ExampleObjectSerializer extends ObjectSerializer\u003cExampleObject\u003e {\n          @Override\n          protected void serializeObject(@NotNull SerializationContext context, @NotNull SerializerOutput output,\n                  @NotNull ExampleObject object) throws IOException {\n              output\n                  .writeInt(object.num) // first field\n                  .writeObject(object.obj, SubObject.SERIALIZER); // second field\n          }\n\n          @Override\n          @NotNull\n          protected ExampleObject deserializeObject(@NotNull SerializationContext context, @NotNull SerializerInput input,\n                  int versionNumber) throws IOException, ClassNotFoundException {\n              final int num = input.readInt(); // first field\n              final SubObject obj = input.readObject(SubObject.SERIALIZER); // second field\n              return new ExampleObject(num, obj);\n          }\n      }\n  }\n\n**译者注：**\n\n这个内部类和 ``parcelable`` 中的 ``Parcelable.Creator`` 极为相似，都是按顺序对变量进行读写操作。为了方便理解，可以和Parcelable.Creator做下类比：\n\n.. code-block:: java\n\n  public static final Parcelable.Creator\u003cPerson\u003e CREATOR = new Creator\u003cPerson\u003e() {\n\n      @Override\n      public Person createFromParcel(Parcel source) {\n          Person person = new Person();\n          person.mName = source.readString();\n          person.mSex = source.readString();\n          person.mAge = source.readInt();\n          return person;\n      }\n\n      //供反序列化本类数组时调用的方法\n      @Override\n      public Person[] newArray(int size) {\n          return new Person[size];\n      }\n  };\n\n对于那些通过builder模式构建的类或是有多个构造方法的类（详见：`更新Serializers`_ ），你可以使用 ``BuilderSerializer`` 来做序列化。\n\n你只需要继承 ``BuilderSerializer`` ，并实现 ``createBuilder`` 方法（仅return当前class的builder即可）和 ``deserializeToBuilder`` 方法（在这个方法中可以得到builder对象，这里将那些反序列化完毕的参数重新设置给builder）\n\n.. code-block:: java\n\n  public static class ExampleObject {\n      ...\n\n      public ExampleObject(@NotNull Builder builder) {\n          this.num = builder.mNum;\n          this.obj = builder.mObj;\n      }\n\n      ...\n\n      public static class Builder extends ModelBuilder\u003cExampleObject\u003e {\n          ...\n      }\n\n      private static final class ExampleObjectSerializer extends BuilderSerializer\u003cExampleObject, Builder\u003e {\n          @Override\n          @NotNull\n          protected Builder createBuilder() {\n              return new Builder();\n          }\n\n          @Override\n          protected void serializeObject(@NotNull SerializationContext context, @NotNull SerializerOutput output,\n                  @NotNull ExampleObject object) throws IOException {\n              output.writeInt(object.num)\n                  .writeObject(object.obj, SubObject.SERIALIZER);\n          }\n\n           @Override\n          protected void deserializeToBuilder(@NotNull SerializationContext context, @NotNull SerializerInput input,\n                  @NotNull Builder builder, int versionNumber) throws IOException, ClassNotFoundException {\n              builder.setNum(input.readInt())\n                  .setObj(input.readObject(SubObject.SERIALIZER));\n          }\n      }\n  }\n\n序列化工具方法\n-----------------------------\n- ``CoreSerializers`` and ``CollectionSerializers`` 提供了一些静态方法来方便collections，enums，comparators对象被序列化。\n\n  - 比如，当我们序列化一个string列表的时候可以这么做:\n\n    .. code-block:: java\n\n      CollectionSerializers.getListSerializer(Serializers.STRING);\n\n- 对于那些有基类的对象，你可以用 ``CoreSerializers`` 中的getBaseClassSerializer()，它会通过子类serializers构造出基类的serializer。\n\n  - 举个例子，比如ClassA和ClassB都继承自ClassC。你想要将当前对象序列化为ClassC的类型，你可以在ClassC中通过子类的serializer方法来建立一个SERIALIZER。\n\n    .. code-block:: java\n\n      final Serializer\u003cClassC\u003e SERIALIZER = CoreSerializers.getBaseClassSerializer(\n            SerializableClass.create(ClassA.class, new ClassA.ClassASerializer()),\n            SerializableClass.create(ClassB.class, new ClassB.ClassBSerializer()));\n\n  .. \n  注意::\n    这里必须new出ClassA和ClassB的serializer对象（new ClassA.ClassASerializer()、ClassB.ClassBSerializer()），而不是直接使用在ClassA和ClassB中定义的静态serializer。\n\n\n更新Serializers\n--------------------\n如果你在新版本App中添加或删除了之前已经被序列化的对象的field，那么在反序列化老版本数据的时候可能会碰到一些问题。\n\n下面有几种方案可以来处理这种情况：\n\n``OptionalFieldException``\n~~~~~~~~~~~~~~~~~~~~~~~~~~\n\n当你在新版本的ExampleObject添加了一个新的字段，这时反序列化老版本ExampleObject就会出问题。Serializer默认会依次的读取所有的field，此时抛出 ``OptionalFieldException`` 异常。\n\n``BuilderSerializer`` 已经为你处理好了 ``OptionalFieldExceptions`` 。当它捕获到这个异常时会终止序列化过程并忽略你这个新加的field，立刻返回一个没有这个field的对象。如果你使用的是普通的Serializer，那么你可以通过try-catch来处理这个问题。\n\n- 举个例子：比如你想要给ExampleObject的最后增加一个叫 ``name`` 的字段（原先的ExampleObject仅有num和SubObject这两个字段）\n\n  - 对于都是serializer类型的情况，只需简单的添加 ``.writeString(obj.name)`` 到 ``serializeObject`` 中即可\n  - 对于BuilderSerializer，只需要在 ``deserializeToBuilder`` 的最后添加 ``.setName(input.readString())`` 即可\n  - 对于普通的Serializer，你必须要修改像下面一样修改 ``deserializeObject`` 方法:\n\n    .. code-block:: java\n\n      @Override\n      @NotNull\n      protected ExampleObject deserializeObject(@NotNull SerializationContext context, @NotNull SerializerInput input, int versionNumber) throws IOException, ClassNotFoundException {\n          final int num = input.readInt();\n          final SubObject obj = input.readObject(SubObject.SERIALIZER);\n          final String name;\n          try {\n              name = input.readString();\n          } catch (OptionalFieldException e) {\n              name = DEFAULT_NAME; // 老版本中没有这个字段，给它一个默认值\n          }\n          return new ExampleObject(num, obj, name);\n      }\n\n版本号\n~~~~~~~~~~~~~~~\n你可以给你的serializer添加一个版本号，这样当你在反序列化的过程中就可以通过这个版本号来进行复杂的处理了。添加版本号十分简单，只需要在 ``SERIALIZER`` 的构造函数中传入数字即可。\n\n- 我们来修改一下上面的代码，通过版本号这个字段来处理新老版本的问题：\n\n  .. code-block:: java\n\n    final Serializer\u003cExampleObject\u003e SERIALIZER = new ExampleObjectSerializer(1);\n    ...\n\n    @Override\n    @NotNull\n    protected ExampleObject deserializeObject(@NotNull SerializationContext context, @NotNull SerializerInput input, int versionNumber) throws IOException, ClassNotFoundException {\n        final int num = input.readInt();\n        final SubObject obj = input.readObject(SubObject.SERIALIZER);\n        final String name;\n        if (versionNumber \u003c 1) {\n            name = DEFAULT_NAME;\n        } else {\n            name = input.readString();\n        }\n        return new ExampleObject(num, obj, name);\n    }\n\n如果你删除了序列化对象中部的某个field，比如ExampleObject中间的 ``SubObject`` 。你可能需要用 ``SerializationUtils.skipObject()`` 来终止整个反序列化过程。如果你已经把 ``SubObject`` 完全移除了，那么可以不用保留 ``SubObject`` 中的serializer对象。\n\n- 比方说，你可能在新版本中删除了 ``SubObject`` ，而老版本的数据中含有这个对象，你可以进行下面的处理:\n\n  .. code-block:: java\n\n    @Override\n    @NotNull\n    protected ExampleObject deserializeObject(@NotNull SerializationContext context, @NotNull SerializerInput input, int versionNumber)\n            throws IOException, ClassNotFoundException {\n        final int num = input.readInt();\n        if (versionNumber \u003c 1) {\n            SerializationUtils.skipObject()\n            name = DEFAULT_NAME;\n        } else {\n            name = input.readString();\n        }\n        return new ExampleObject(num, name);\n    }\n\n另一个方法是调用input.peekType()。这个方法可以让你在读取object对象前进行下一个参数的类型检查，它提供了一个除判断版本号之外的解决新老数据的问题的方案。当你不愿意升级版本号或是不愿意擦除数据库的时候，这个方法会十分有用。\n\n需要注意的是：这个方法仅仅适用于两个对象类型不同的情况。因为这里obj类型是 ``SubObject`` ，name类型是 ``String`` ，所以可以进行如下处理：\n\n.. code-block:: java\n\n    @Override\n    @NotNull\n    protected ExampleObject deserializeObject(@NotNull SerializationContext context, @NotNull SerializerInput input, int versionNumber) throws IOException, ClassNotFoundException {\n        final int num = input.readInt();\n        if (input.peekType() == SerializerDefs.TYPE_START_OBJECT) {\n            SerializationUtils.skipObject();\n            name = DEFAULT_NAME;\n        } else {\n            name = input.readString();\n        }\n        return new ExampleObject(num, name);\n    }\n\n简单参数的序列化\n-----------------\n像 ``Integer`` 、 ``String`` 、 ``Size``、``Rect`` 等对象本身就十分简单，所以无需进行版本控制。而使用 ``ObjectSerializer`` 会让这些对象添加2-3字节的信息。所以，当不需要版本控制的时候，使用 ``ValueSerializer`` 是一个最佳选择：\n\n.. code-block:: java\n\n  public static final Serializer\u003cBoolean\u003e BOOLEAN = new ValueSerializer\u003cBoolean\u003e() {\n      @Override\n      protected void serializeValue(@NotNull SerializationContext context, @NotNull SerializerOutput output, @NotNull Boolean object) throws IOException {\n          output.writeBoolean(object);\n      }\n\n      @NotNull\n      @Override\n      protected Boolean deserializeValue(@NotNull SerializationContext context, @NotNull SerializerInput input) throws IOException {\n          return input.readBoolean();\n      }\n  };\n\n这仅仅是 ``ObjectSerializer`` 的简单版本，它处理了 ``null`` 的情况。否则，只需将值写入到流中。\n\n.. \n说明::\n\n让值为null的时候 ``ValueSerializer`` 会将 ``null`` 写入到流中。这就导致第一个通过 ``serializeValue`` 写入到流中的参数（field）不能为 ``null`` ，否则就会引起歧义。在这种情况下， ``ValueSerializer`` 会认为这是一个错误，并且抛出异常。\n\n..\n警告:: \n\n  ValueSerializers“仅仅”能被用于对象格式已知的情况下，也就是说它不能向后兼容。\n\n调试\n---------\n``serial`` 同样也提供了方便debug的相关方法：\n\n- ``dumpSerializedData`` 会根据序列化后的byte[]数据产生string类型的log\n- ``validateSerializedData`` 确保了序列化后的对象有有效的结构(比如每个对象都有开头和结尾)\n\nSerial的异常信息中会包含很多序列化失败的原因，比如期望的类型和实际类型不匹配这种常见错误。\n","project_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Ftwitter%2Fserial","html_url":"https://awesome.ecosyste.ms/projects/github.com%2Ftwitter%2Fserial","lists_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Ftwitter%2Fserial/lists"}