5 Star 13 Fork 6

darks / darks-codec

加入 Gitee
与超过 1200万 开发者一起发现、参与优秀开源项目,私有仓库也完全免费 :)
免费加入
克隆/下载
贡献代码
同步代码
取消
提示: 由于 Git 不支持空文件夾,创建文件夹后会生成空的 .keep 文件
Loading...
README
Apache-2.0

Darks Codec

Darks codec is a lightweight message protocol encoding and decoding framework. It supports encoding and decoding message object of most message protocol based on bytes. It helps developers build any message protocol easily and quickly. And help to solve network communication protocol TCP's stick package and broken package problem. It makes developers design attention more than the implementation of message protocol, which can help software design better.

Simple Example

Define Message Structure

If we want to build the message protocol with LITTLE-ENDIAN like:

  FB FA  [ID 32bits] [VERSION 8bits] [COMMAND]  FF

We can build JAVA class like:

  public class SimpleMsg
  {
      int id;
      byte version;
      String command;
  }

In order to describe simple, we omit get/set method.

Configure Object Coder

According to message protocol, we only need Head identify "FB FA" and tail identify "FF" besides message body, so we can configure object coder like:

  ObjectCoder coder = new ObjectCoder();
  coder.getCodecConfig().setEndianType(EndianType.LITTLE);
  coder.getCodecConfig().addWrap(new IdentifyWrapper(new OCInt16(0xFAFB), new OCInt8(0xFF)));

Encoding Message

Now we can encode message object easily.

  SimpleMsg msg = new SimpleMsg();
  msg.id = 32;
  msg.version = 1;  
  msg.command = "running";
  byte[] bytes = coder.encode(msg);
  System.out.println(ByteHelper.toHexString(bytes));

Code will output console information:

  FB FA   20 00 00 00   01   72 75 6E 6E 69 6E 67   FF

Because of LITTLE-ENDIAN, 0xFAFB coded as "FB FA", ID which is 32 coded as "20 00 00 00", VERSION which is 1 coded as "01", command which is "running" coded as "72 75 6E 6E 69 6E 67" and 0xFF coded as "FF".

Decoding Message

Now we try to decode message object easily.

  SimpleMsg result = new SimpleMsg();
  coder.decode(bytes, result);
  System.out.println("ID:" + result.id);
  System.out.println("VERSION:" + result.version);
  System.out.println("COMMAND:" + result.command);

Code will output console information:

  ID:32
  VERSION:1
  COMMAND:running

Total Length

Some message protocol need replace tail identify with bytes total length. We can set total length type to have the bytes total length. Total length type have AUTO, BODY and HEAD_BODY types.
AUTO : Automatic object total length. It calculate object length without head or tail wrapper's length only when autoLength is true.
BODY : Body total length will calculate object length and tail wrapper's length without head wrapper's length.
HEAD_BODY : Head and body total length will calculate head wrapper, tail wrapper and object length.

  ObjectCoder coder = new ObjectCoder();
  coder.getCodecConfig().setEndianType(EndianType.LITTLE);
  coder.getCodecConfig().setTotalLengthType(TotalLengthType.HEAD_BODY);
  coder.getCodecConfig().addWrap(new IdentifyWrapper(new OCInt16(0xFAFB)));

Code will output console information:

  FB FA   12 00 00 00   20 00 00 00   01   72 75 6E 6E 69 6E 67 

Now, we have finished a simple example. You can find codes in /examples/darks/codec/examples/simple.

Automatic Value Length

If message protocol have multiply object type such as String, Object, Bytes and so on, we should set automatic length to ensure decoding message correctly.
Message protocol may like:

  FB FA  [TOTAL LENGTH] [ID 32bits] [VERSION 8bits] [CMD1 LEN 32bits] [COMMAND1] [CMD2 LEN 32bits] [COMMAND2]

Java bean class:

  public class MultiCmdMsg
  {
      int id;
      byte version;
      String command1;
      String command2;
  }

Then we encode it object will automatic length:

  ObjectCoder coder = new ObjectCoder();
  coder.getCodecConfig().setEndianType(EndianType.LITTLE);
  coder.getCodecConfig().setTotalLengthType(TotalLengthType.HEAD_BODY);
  coder.getCodecConfig().setAutoLength(true);
  coder.getCodecConfig().addWrap(new IdentifyWrapper(new OCInt16(0xFAFB)));
  MultiCmdMsg msg = new MultiCmdMsg();
  msg.id = 32;
  msg.version = 1;
  msg.command1 = "ready";
  msg.command2 = "running";
  byte[] bytes = coder.encode(msg);
  System.out.println(ByteHelper.toHexString(bytes));

Code will output console information:

  FB FA   1F 00 00 00   20 00 00 00   01   05 00 00 00   72 65 61 64 79   07 00 00 00   72 75 6E 6E 69 6E 67

You can see detail example codes in /examples/darks/codec/examples/autolen.

Codec Type

Besides using JAVA type directly, developers can use codec type which is in package darks.codec.type more flexibly to code.
OCInt32 : 32-bits integer type which based on OCInteger.
OCInt16 : 16-bits integer type which based on OCInteger.
OCInt8 : 8-bits integer type which based on OCInteger.
OCLong : 64-bits long type.
OCFloat : Just like float.
OCDouble: Just like double.
OCBytes : Bytes array type.
OCString: Just like String.
OCList : It can store collection data which based on java.util.List.
OCMap : It can store Key-value pair values which based on java.util.Map.
OCListMap: It can store multiply values in same key index besides Map feature.
OCObject: Java object can extends it to code flexibly.
Custom Type: Developers can build a class which inherit from OCBase or OCBaseType to customize type, which must add annotation @CodecType.

Codec Type Example

We can rebuild SimpleMsg by codec type.

  public class SimpleMsg extends OCObject
  {
      OCInt32 id = new OCInt32();
      OCInt8 version = new OCInt8();
      OCString command = new OCString();
  }

Also we can rebuild MultiCmdMsg by mix type.

  public class MultiCmdMsg
  {
      int id;
      byte version;
      OCInt32 cmdLen1 = new OCInt32();
      OCString command1 = new OCString(cmdLen1);
      OCInt32 cmdLen2 = new OCInt32();
      OCString command2 = new OCString(cmdLen2);
  }

"command1 = new OCString(cmdLen1)" can set command1's length value to field "cmdLen1" automatically. And It will decode command1 by cmdLen1's value when decoding. Therefore we should set parameter "autoLength" false.

  ObjectCoder coder = new ObjectCoder();
  coder.getCodecConfig().setEndianType(EndianType.LITTLE);
  coder.getCodecConfig().setTotalLengthType(TotalLengthType.HEAD_BODY);
  coder.getCodecConfig().setAutoLength(false);  //default false.
  coder.getCodecConfig().addWrap(new IdentifyWrapper(new OCInt16(0xFAFB)));
  MultiCmdMsg msg = new MultiCmdMsg();
  msg.id = 32;
  msg.version = 1;
  msg.command1.setValue("ready");
  msg.command2.setValue("running");
  byte[] bytes = coder.encode(msg);
  System.out.println(ByteHelper.toHexString(bytes));

You can see detail example codes in /examples/darks/codec/examples/codectype.

Complex Message

We can try to build a multiple nested object. The message protocol just like:

  FA FB [TOTAL LEN 32bits] [ID 32bits] [VERSION 8bits] [EXTERN LEN 16bits] [EXTERN BYTES] [SUB LEN 32 bits] [#SUB MSG#[CODE LEN 8bits] [CODE] [MODULAR 8bits] [SUB MODULAR 8bits] [#CMDS#[CMD CODE 8bits] [CODE length 16bits] [CODE] ... [CMD CODE 8bits] [CODE length 16bits] [CODE]]]

We can build JAVA bean like:

public class ComplexMsg
{
    int id;
    
    byte version;
    
    OCInt16 externLength = new OCInt16();
    
    OCBytes extern = new OCBytes(externLength);
    
    OCInt32 subMsgLength = new OCInt32();
    
    ComplexSubMsg subMsg = new ComplexSubMsg(subMsgLength);
}

class ComplexSubMsg extends OCObject
{

    OCInt8 codeLen = new OCInt8();
    
    OCString equipCode = new OCString(codeLen);
    
    byte modular;
    
    byte subModular;
    
    OCMap commands = new OCMap();
    
    public ComplexSubMsg(OCInteger lenType)
    {
        super(lenType);
    }
    
}

class OrderMsg
{
    OCInt16 orderLength = new OCInt16();
    
    OCBytes order = new OCBytes(orderLength);

    public OrderMsg()
    {
    }
    
    public OrderMsg(OCBytes order)
    {
        this.order = order;
        order.setLenType(orderLength);
    }
    
}

Then we encode the message.

ObjectCoder coder = new ObjectCoder();
coder.getCodecConfig().setEndianType(EndianType.LITTLE);
coder.getCodecConfig().setTotalLengthType(TotalLengthType.HEAD_BODY);
coder.getCodecConfig().addWrap(new IdentifyWrapper(new OCInt16(0xfafb)));

ComplexMsg msg = new ComplexMsg();
msg.id = 32;
msg.version = 1;
msg.subMsg.equipCode.setValue("2014");
msg.subMsg.modular = 0x08;
msg.subMsg.subModular = 0x01;
msg.subMsg.commands.put((byte)0x01, new OrderMsg(OCBytes.valueOf("ready")));
msg.subMsg.commands.put((byte)0x02, new OrderMsg(OCBytes.valueOf(128, true)));
msg.subMsg.commands.put((byte)0x03, new OrderMsg(OCBytes.valueOf("parameter")));

Code will output console information:

  FB FA   33 00 00 00   20 00 00 00   01   00 00   22 00 00 00  #SUB MSG#04   32 30 31 34   08   01  #CMDS#03   09 00   70 61 72 61 6D 65 74 65 72   01   05 00   72 65 61 64 79   02   04 00   80 00 00 00

We can also decode the bytes.

ComplexMsg result = new ComplexMsg();
coder.decode(bytes, result);

OCMap<Byte, OrderMsg> cmds = result.subMsg.commands; System.out.println("ID:" + result.id + " VERSION:" + result.version); System.out.println("Equip Code:" + result.subMsg.equipCode.getValue()); System.out.println("Modular:" + result.subMsg.modular + " Sub Modular:" + result.subMsg.subModular); System.out.println("Command 01:" + cmds.get((byte)0x01).order.getString()); System.out.println("Command 02:" + cmds.get((byte)0x02).order.getInt32(true)); System.out.println("Command 03:" + cmds.get((byte)0x03).order.getString());

Code will output console information:
ID:32 VERSION:1
Equip Code:2014
Modular:8 Sub Modular:1
Command 01:ready
Command 02:128
Command 03:parameter

Simple Serialization

To replace the large bytes and coding slowly of JAVA serialization, we can use darks-codec's simple serialization instead. It only contains the full name of main class and object's data. Even it can use ObjectCoder's setting such as wrappers, total length and so on. Object doesn't needs to implement interface java.io.Serializable. It can be serialized directly.
If we have a JAVA bean just like:

class SerialMainBean
{
    int id;
    int version;
    SerialSub subSerial;
}

class SerialSubBean
{
    String equip;
    int code;
    String content;
}

Then we configure object coder and build a SerialMainBean object. If you build JAVA bean without codec type, you should set automatic length true.

ObjectCoder coder = new ObjectCoder();
coder.getCodecConfig().setEndianType(EndianType.LITTLE);
coder.getCodecConfig().setTotalLengthType(TotalLengthType.HEAD_BODY);
coder.getCodecConfig().setAutoLength(true);
coder.getCodecConfig().setCacheType(CacheType.LOCAL);
coder.getCodecConfig().addWrap(new IdentifyWrapper((short)0xfafb));
coder.getCodecConfig().addWrap(VerifyWrapper.CRC16());

SerialMainBean bean = new SerialMainBean();
bean.id = 128;
bean.version = 1;
bean.subSerial = new SerialSubBean();
bean.subSerial.code = 10;
bean.subSerial.content = "running";
bean.subSerial.equip = "2014";

Then we can serial object to bytes.

byte[] bytes = ObjectSerial.encode(coder, bean);

And we can convert bytes to object.

Object result = ObjectSerial.decode(coder, bytes);

Fields Cache

To encode or decode object, darks-codec will get object's valid fields. We can use field cache to improve the speed of getting fields. Cache have LOCAL and GLOBAL type. Default NONE.
LOCAL : Local cache is available in current ObjectCoder.
GLOBAL: Global cache is available in all ObjectCoder as global static object.

  ObjectCoder coder = new ObjectCoder();
  coder.getCodecConfig().setEndianType(EndianType.LITTLE);
  coder.getCodecConfig().setCacheType(CacheType.LOCAL);
    ...

Field Sequence

In some Android's dalvikVM, the fields get from object are sorted automatically by virtual machine. Therefore we cannot encode object fields according to the specified fields sequence. To solve the problem, we should define a field named "fieldSequence" in JAVA object or use OCObject's method "setFieldSequence". Java bean class like:

  public class FieldMsg
  {
      static String[] fieldSequence = new String[]{"id", "version", "command"};
      String command;
      int id;
      byte version;
  }

Or

  public class FieldCodecMsg extends OCObject
  {
      public FieldCodecMsg()
      {
          setFieldSequence(new String[]{"id", "version", "command"});
      }
      OCString command = new OCString();
      int id;
      byte version;
  }

You can see detail example codes in /examples/darks/codec/examples/fieldseq.

Wrapper

When ObjectCoder encoding or decoding message, It will use WrapperChain to call wrapper before and after encoding or decoding. When developers add wrapper, wrapper will be added to the first of chain.
When encoding message, wrappers are called like LIFO, which will call the first addition of wrapper finally. And when decoding message, wrappers are called like FIFO, which will call the first addition of wrapper firstly.
Example:

addWrap IdentifyWrapper
addWrap VerifyWrapper
addWrap ZipWrapper

Encoding call sequence:
ZipWrapper -> VerifyWrapper -> IdentifyWrapper

Decoding call sequence:
IdentifyWrapper -> VerifyWrapper -> ZipWrapper

TotalLengthWrapper

TotalLengthWrapper will be added automatically when total length type is BODY or HEAD_BODY, so developers cannot add it manually again.

Identify Wrapper

IdentifyWrapper can help developers add head identify and tail identify. You can add only head identify or both of them.

  ObjectCoder coder = new ObjectCoder();
  coder.getCodecConfig().addWrap(new IdentifyWrapper(new OCInt16(0xFAFB), new OCInt8(0xFF)));
    ...
  coder.getCodecConfig().addWrap(new IdentifyWrapper(new OCInt16(0xFAFB)));
    ...
  coder.getCodecConfig().addWrap(new IdentifyWrapper(new OCInt8(0xFA)));
    ...
  coder.getCodecConfig().addWrap(new IdentifyWrapper((short)0xFAFB));

Verify Wrapper

VerifyWrapper can add verify bytes to the end of message bytes such as CRC16, CRC32, ADLER32 and so on.

  ObjectCoder coder = new ObjectCoder();
  coder.getCodecConfig().addWrap(VerifyWrapper.CRC16());
    ...
  coder.getCodecConfig().addWrap(VerifyWrapper.CRC32());
    ...
  coder.getCodecConfig().addWrap(new VerifyWrapper(new CustomVerifier()));

Example:

  ObjectCoder coder = new ObjectCoder();
  coder.getCodecConfig().setEndianType(EndianType.LITTLE);
  coder.getCodecConfig().setTotalLengthType(TotalLengthType.HEAD_BODY);
  coder.getCodecConfig().addWrap(new IdentifyWrapper(new OCInt16(0xFAFB)));
  coder.getCodecConfig().addWrap(VerifyWrapper.CRC16());
  
  SimpleMsg msg = new SimpleMsg();
  msg.id = 32;
  msg.version = 1;  
  msg.command = "running";
  byte[] bytes = coder.encode(msg);
  System.out.println(ByteHelper.toHexString(bytes));

Code will output console information:

  FB FA   14 00 00 00   20 00 00 00   01   72 75 6E 6E 69 6E 67   D6 74 

"D6 74" is the message bytes's CRC16 code.

ZIP Wrapper

If message bytes are so large, we can compress bytes to reduce communication traffic. It supports JDK GZIP, JZLIB (Need jzlib-1.1.x.jar), Commons Compress(Need commons-compress-1.x.jar) and custom compress.

  ObjectCoder coder = new ObjectCoder();
  coder.getCodecConfig().addWrap(ZipWrapper.JZLIB());
    ...
  coder.getCodecConfig().getWrapChain().add(ZipWrapper.COMMON_COMPRESS(CompressorStreamFactory.BZIP2));
    ...
  coder.getCodecConfig().addWrap(new ZipWrapper(new CustomZip()));

Cipher Wrapper

Developers can encrypt message bytes to ensure information secure.

  ObjectCoder coder = new ObjectCoder();
  coder.getCodecConfig().addWrap(CipherWrapper.AES("AESKEYS"));
    ...
  coder.getCodecConfig().addWrap(new CipherWrapper(new CustomCipher()));

I wish you a pleasant to use darks-codec. If you have some good advice or bug report, please share with us. Thank you!

Apache License Version 2.0, January 2004 http://www.apache.org/licenses/ TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION 1. Definitions. "License" shall mean the terms and conditions for use, reproduction, and distribution as defined by Sections 1 through 9 of this document. "Licensor" shall mean the copyright owner or entity authorized by the copyright owner that is granting the License. "Legal Entity" shall mean the union of the acting entity and all other entities that control, are controlled by, or are under common control with that entity. For the purposes of this definition, "control" means (i) the power, direct or indirect, to cause the direction or management of such entity, whether by contract or otherwise, or (ii) ownership of fifty percent (50%) or more of the outstanding shares, or (iii) beneficial ownership of such entity. "You" (or "Your") shall mean an individual or Legal Entity exercising permissions granted by this License. "Source" form shall mean the preferred form for making modifications, including but not limited to software source code, documentation source, and configuration files. "Object" form shall mean any form resulting from mechanical transformation or translation of a Source form, including but not limited to compiled object code, generated documentation, and conversions to other media types. "Work" shall mean the work of authorship, whether in Source or Object form, made available under the License, as indicated by a copyright notice that is included in or attached to the work (an example is provided in the Appendix below). "Derivative Works" shall mean any work, whether in Source or Object form, that is based on (or derived from) the Work and for which the editorial revisions, annotations, elaborations, or other modifications represent, as a whole, an original work of authorship. For the purposes of this License, Derivative Works shall not include works that remain separable from, or merely link (or bind by name) to the interfaces of, the Work and Derivative Works thereof. "Contribution" shall mean any work of authorship, including the original version of the Work and any modifications or additions to that Work or Derivative Works thereof, that is intentionally submitted to Licensor for inclusion in the Work by the copyright owner or by an individual or Legal Entity authorized to submit on behalf of the copyright owner. For the purposes of this definition, "submitted" means any form of electronic, verbal, or written communication sent to the Licensor or its representatives, including but not limited to communication on electronic mailing lists, source code control systems, and issue tracking systems that are managed by, or on behalf of, the Licensor for the purpose of discussing and improving the Work, but excluding communication that is conspicuously marked or otherwise designated in writing by the copyright owner as "Not a Contribution." "Contributor" shall mean Licensor and any individual or Legal Entity on behalf of whom a Contribution has been received by Licensor and subsequently incorporated within the Work. 2. Grant of Copyright License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare Derivative Works of, publicly display, publicly perform, sublicense, and distribute the Work and such Derivative Works in Source or Object form. 3. Grant of Patent License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable (except as stated in this section) patent license to make, have made, use, offer to sell, sell, import, and otherwise transfer the Work, where such license applies only to those patent claims licensable by such Contributor that are necessarily infringed by their Contribution(s) alone or by combination of their Contribution(s) with the Work to which such Contribution(s) was submitted. If You institute patent litigation against any entity (including a cross-claim or counterclaim in a lawsuit) alleging that the Work or a Contribution incorporated within the Work constitutes direct or contributory patent infringement, then any patent licenses granted to You under this License for that Work shall terminate as of the date such litigation is filed. 4. Redistribution. You may reproduce and distribute copies of the Work or Derivative Works thereof in any medium, with or without modifications, and in Source or Object form, provided that You meet the following conditions: (a) You must give any other recipients of the Work or Derivative Works a copy of this License; and (b) You must cause any modified files to carry prominent notices stating that You changed the files; and (c) You must retain, in the Source form of any Derivative Works that You distribute, all copyright, patent, trademark, and attribution notices from the Source form of the Work, excluding those notices that do not pertain to any part of the Derivative Works; and (d) If the Work includes a "NOTICE" text file as part of its distribution, then any Derivative Works that You distribute must include a readable copy of the attribution notices contained within such NOTICE file, excluding those notices that do not pertain to any part of the Derivative Works, in at least one of the following places: within a NOTICE text file distributed as part of the Derivative Works; within the Source form or documentation, if provided along with the Derivative Works; or, within a display generated by the Derivative Works, if and wherever such third-party notices normally appear. The contents of the NOTICE file are for informational purposes only and do not modify the License. You may add Your own attribution notices within Derivative Works that You distribute, alongside or as an addendum to the NOTICE text from the Work, provided that such additional attribution notices cannot be construed as modifying the License. You may add Your own copyright statement to Your modifications and may provide additional or different license terms and conditions for use, reproduction, or distribution of Your modifications, or for any such Derivative Works as a whole, provided Your use, reproduction, and distribution of the Work otherwise complies with the conditions stated in this License. 5. Submission of Contributions. Unless You explicitly state otherwise, any Contribution intentionally submitted for inclusion in the Work by You to the Licensor shall be under the terms and conditions of this License, without any additional terms or conditions. Notwithstanding the above, nothing herein shall supersede or modify the terms of any separate license agreement you may have executed with Licensor regarding such Contributions. 6. Trademarks. This License does not grant permission to use the trade names, trademarks, service marks, or product names of the Licensor, except as required for reasonable and customary use in describing the origin of the Work and reproducing the content of the NOTICE file. 7. Disclaimer of Warranty. Unless required by applicable law or agreed to in writing, Licensor provides the Work (and each Contributor provides its Contributions) on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied, including, without limitation, any warranties or conditions of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A PARTICULAR PURPOSE. You are solely responsible for determining the appropriateness of using or redistributing the Work and assume any risks associated with Your exercise of permissions under this License. 8. Limitation of Liability. In no event and under no legal theory, whether in tort (including negligence), contract, or otherwise, unless required by applicable law (such as deliberate and grossly negligent acts) or agreed to in writing, shall any Contributor be liable to You for damages, including any direct, indirect, special, incidental, or consequential damages of any character arising as a result of this License or out of the use or inability to use the Work (including but not limited to damages for loss of goodwill, work stoppage, computer failure or malfunction, or any and all other commercial damages or losses), even if such Contributor has been advised of the possibility of such damages. 9. Accepting Warranty or Additional Liability. While redistributing the Work or Derivative Works thereof, You may choose to offer, and charge a fee for, acceptance of support, warranty, indemnity, or other liability obligations and/or rights consistent with this License. However, in accepting such obligations, You may act only on Your own behalf and on Your sole responsibility, not on behalf of any other Contributor, and only if You agree to indemnify, defend, and hold each Contributor harmless for any liability incurred by, or claims asserted against, such Contributor by reason of your accepting any such warranty or additional liability. END OF TERMS AND CONDITIONS APPENDIX: How to apply the Apache License to your work. To apply the Apache License to your work, attach the following boilerplate notice, with the fields enclosed by brackets "[]" replaced with your own identifying information. (Don't include the brackets!) The text should be enclosed in the appropriate comment syntax for the file format. We also recommend that a file or class name and description of purpose be included on the same "printed page" as the copyright notice for easier identification within third-party archives. Copyright [yyyy] [name of copyright owner] Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0 Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.

简介

Darks Codec是一个轻量级的通信消息协议编解码框架。为开发人员提供便捷快速有效的通信消息协议构建方案。 展开 收起
Java
Apache-2.0
取消

发行版

暂无发行版

贡献者

全部

近期动态

加载更多
不能加载更多了
Java
1
https://gitee.com/darks/darks-codec.git
git@gitee.com:darks/darks-codec.git
darks
darks-codec
darks-codec
master

搜索帮助